Lightning App Builder
Lightning App Builder is a Setup tool that provides a drag-and-drop interface for creating and customizing Lightning record pages, app pages, and home pages.
Definition
Lightning App Builder is a Setup tool that provides a drag-and-drop interface for creating and customizing Lightning record pages, app pages, and home pages. Administrators can add standard and custom Lightning components, configure their properties, and assign pages to specific apps, record types, and profiles without writing code.
In plain English
“Here's a simple way to think about it: Lightning App Builder is where most page-level customization actually happens. Drag-and-drop record pages, app pages, home pages - the modern equivalent of Page Layout, with more capability and more nuance.”
Worked example
The admin at Forge Dynamics uses Lightning App Builder to create a custom Account record page. She drags in the Record Detail component, an Activity Timeline, a custom LWC that shows real-time stock data, and a Related List for Opportunities. She activates the page as the org default for Accounts, giving the sales team a richer, more informative view.
Why Lightning App Builder is where most page-level customization actually happens
Lightning App Builder is the drag-and-drop tool for designing record pages, app home pages, and Lightning app pages. Standard components, custom Lightning components, dynamic forms, dynamic related lists - every layout decision a user actually sees is composed here. For modern Salesforce, Lightning App Builder is to record pages what Page Layout was to Salesforce Classic: the canonical authoring surface.
The reason it earns more attention than the Page Layout it largely replaces is that Lightning pages have more capability and more nuance. Component visibility based on record state, multi-column layouts, embedded reports, dynamic forms with field-level visibility rules, role-aware page assignment - none of these existed in the Page Layout era. Master Lightning App Builder for at least the most-used record types in your org; the per-user productivity difference between a thoughtfully-designed Lightning page and a default one is significant.
How to set up Lightning App Builder
Lightning App Builder is the drag-and-drop tool for building Lightning Pages — App Pages, Home Pages, and Record Pages. Lightning Pages override Page Layouts for everything outside the Details tab and are the primary UI customization tool in modern Salesforce.
- Open Setup → Lightning App Builder
Setup gear → Quick Find: Lightning App Builder → Lightning App Builder.
- Click New
Top-right of the Lightning Pages list.
- Pick a Page Type
App Page (a custom tab inside a Lightning App), Home Page (the org's home), or Record Page (a record's detail experience). Most work happens on Record Pages.
- Pick a Template
1-region, 2-region (header-aside), 3-region, etc. The template controls regions you can drop components into.
- Drag components from the left rail
Standard components (Highlights Panel, Tabs, Activity, Related Lists, Path), custom Lightning Web Components, and AppExchange components are all draggable.
- Set component properties on the right rail
Each component has its own property panel. Visibility filters (by Profile / App / Record / Permission Set) hide components from users who don't match.
- Save → Activate
Save the page. Activate scope: Org Default / App Default / App and Profile-specific. Most orgs do App and Profile-specific for fine-grained control.
App Page / Home Page / Record Page. Locked at creation.
1-region / 2-region / 3-region / Pinned Header etc. Drives the canvas layout.
Filter rules per component — hide if Profile != X, hide if Record.Field = Y, etc.
Org Default (single page for everyone) / App Default (per-app default) / App + Profile (per-app per-profile).
- Lightning Record Pages override Page Layouts for everything except the Details tab. If a button or related list isn't appearing, check the Lightning Record Page in Lightning App Builder before assuming the Page Layout is wrong.
- Component Visibility filters are evaluated per-record. Heavy use of complex filters slows down record-page render. Profile filters are cheap; record-field filters are not.
- Activation scope confusion is the #1 admin headache. "Org Default" means literally everyone everywhere, which is rarely what you want — App + Profile is almost always the right choice.
How organizations use Lightning App Builder
Built persona-specific Lightning pages for sales, service, and operations roles; per-role productivity rose measurably.
Dynamic Forms on patient pages show fields conditionally based on care plan stage; clinicians see only the fields relevant to the moment.
Embedded reports on Account pages give reps real-time pipeline context without navigating away.
Trust & references
Straight from the source - Salesforce's reference material on Lightning App Builder.
- Get Help for Lightning App BuilderSalesforce Help
- Create an App Home Page with the Lightning App BuilderSalesforce Help
Test your knowledge
Q1. What architecture concept is Lightning App Builder an example of?
Q2. Who can benefit from understanding Lightning App Builder?
Q3. What does Lightning App Builder represent in the Salesforce Platform?
Discussion
Loading discussion…