Layout
A Layout in Salesforce defines how fields, related lists, and actions appear on a record page.
Definition
A Layout in Salesforce defines how fields, related lists, and actions appear on a record page. The platform supports two distinct layout systems that coexist: Page Layouts (the classic system, still primary for many features) and Lightning Pages (the modern App Builder-driven system for Lightning Experience). Page Layouts control field order, field requirement, and section grouping on record edit and detail views; Lightning Pages control which components render on the record page and where. Most modern orgs use Lightning Pages for the overall page structure and Page Layouts for the field-level form layout within them.
Layouts are assigned per profile and per record type, producing a multidimensional grid where each user sees a specific layout based on their profile and the record's type. This per-assignment model is the source of much administrative complexity in larger orgs: 10 profiles times 5 record types per object produces 50 layout assignments to maintain. Tools like Field Accessibility surface the effective layout per combination, but the underlying assignment matrix is admin-managed and grows linearly with profile and record type counts.
How Salesforce layouts work together
Page Layout (classic) versus Lightning Page
Page Layout is the original Salesforce layout system, dating to Classic UI. It defines field placement on the detail and edit forms, plus related list ordering. Lightning Page is the Lightning Experience layout system built in App Builder; it defines component placement across the entire page (Highlights panel, Tabs, Activity, Chatter, custom components). Both coexist: Lightning Page includes a Record Detail component which renders the Page Layout. Most Lightning orgs configure both.
Field placement and sections
Page Layout Editor lets you organize fields into sections with one or two columns each. Fields can be marked Read-Only or Required at the layout level (different from FLS, which is per-profile). Related lists at the bottom of the layout configure which related objects appear and how. The layout is one of three layers Field Accessibility combines: FLS, page layout property, record type assignment.
Per-profile and per-record-type assignment
Page Layouts are assigned per profile and per record type. The combination determines which layout the user sees. Adding a new profile means assigning page layouts for every record type on every object the profile touches. The setup is tedious but unavoidable; tools and packages help automate but the assignment model is fundamental.
Compact Layout
The Compact Layout is a separate layout type controlling which fields appear in the Highlights panel at the top of the record page (Lightning) and in mobile previews. It is independent of Page Layout; you can have detailed fields in the Page Layout and a curated subset in the Compact Layout. Most orgs configure Compact Layouts deliberately because the Highlights panel is the most prominent field display.
Lightning Page and dynamic components
Lightning Pages are built in App Builder and can use Dynamic Forms (granular field placement in Lightning) and Dynamic Actions. Dynamic Forms replace the classic Page Layout with a more flexible Lightning-native layout, letting administrators place fields directly on the Lightning Page. The path forward for Salesforce is Dynamic Forms; classic Page Layouts remain but are slowly being deprecated in favor of Lightning-native equivalents.
Search Layout
Search Layouts control which columns appear in list views, search results, and lookups. Configured separately from Page Layouts. Each object has its own Search Layouts. The configuration is important for usability: poorly chosen search columns force users to open records to find what they need.
Layout deployment
Layouts are metadata; they deploy through changesets, SFDX, or packages. Layout assignment (which profile gets which layout for which record type) is also metadata and deploys, though large reassignments often have to be done in the target environment for safety. Plan layout deployment carefully because layouts touch the user-facing UI directly.
Configure layouts for a record page
Configuring layouts spans Page Layouts, Lightning Pages, and assignments. The steps below cover the typical setup for a new object or significant page redesign.
- Design the page structure
Sketch what users need to see and do on the record page. Decide which fields are primary (Highlights), which are secondary (form), and which are related list scope.
- Configure Page Layout
Object Manager > Object > Page Layouts. Edit the relevant layout. Organize fields into sections; set Read-Only and Required flags. Configure related lists.
- Configure Compact Layout
Object Manager > Object > Compact Layouts. Edit the primary Compact Layout to show the most important fields in the Highlights panel.
- Build Lightning Page
App Builder. Build the Lightning Page with the components users need (Record Detail, Activity, Files, related lists, custom components). Save and activate.
- Assign layouts to profiles
Object Manager > Object > Page Layouts > Page Layout Assignment. For each profile, assign the appropriate Page Layout for each record type.
- Configure Search Layouts
Object Manager > Object > Search Layouts. Set columns for list views, search results, and lookup dialogs.
- Test from a sample user
Use Login As to impersonate a target user. Confirm the record page displays as expected; verify Highlights, Form, related lists, search results.
Field placement for the form. Coexists with Lightning Page.
Overall page structure including components beyond fields.
Drives the Highlights panel and mobile.
Controls list views, search results, and lookups.
Modern Lightning-native alternative to classic Page Layouts.
- Page Layout and Lightning Page coexist; both need configuration in modern orgs. Configuring only one produces an incomplete user experience.
- Layout assignment is per profile per record type. The assignment matrix grows with both factors; large orgs need disciplined management.
- Compact Layout drives the Highlights panel separately from Page Layout. Forgetting to configure Compact Layout produces a sparse or confusing Highlights area.
- Search Layouts are configured separately. Poor Search Layouts force users to open records to find information that could appear in list views.
- Layouts are deployable metadata. Direct production edits bypass change management and can introduce regressions; deploy through changesets or SFDX.
Trust & references
Straight from the source - Salesforce's reference material on Layout.
- Create Page LayoutsSalesforce Help
- The Enhanced Page Layout EditorSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does a Page Layout define?
Q2. How are page layouts assigned?
Q3. What modern Lightning feature provides finer-grained control?
Discussion
Loading discussion…