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.