Salesforce Page Layouts: Complete Guide
Quick Summary:
Page layouts control which fields, related lists, and buttons appear on a record, and in what order, per profile and record type combination. Setup takes 10-15 minutes per layout.
What Is a Page Layout?
A page layout defines the visual structure of a record detail page — which fields appear, in what sections, which related lists show below, and what buttons are available. Different profiles (and record types) can be assigned different layouts for the same object, letting a sales rep and a support agent see genuinely different views of the same Account.
⚠️ Before You Start
Page layouts are not a security mechanism. Hiding a field from a layout doesn't prevent access to that field's data through reports, list views, or the API — only field-level security actually restricts access.
How to Configure One
Go to the object's Page Layouts section in Object Manager.
Select an existing layout to edit, or clone one as a starting point for a new layout.
Drag fields into sections, arranging them in a logical reading order.
Add, remove, and reorder related lists in the lower portion of the layout.
Configure the button section (standard and custom buttons/links).
Save, then go to Page Layout Assignment to assign this layout to the correct profile/record-type combinations.
🚫 Common Mistake
Editing a layout and assuming the change applies everywhere immediately. Layout assignment is per profile and per record type — a change to one layout doesn't affect other layouts assigned to different profiles, even on the same object.
💡 Pro Tip
Use layout-level required fields sparingly for context-specific requirements, and rely on validation rules for anything that must be enforced regardless of how the record is edited (API, Data Loader, Flow) — layout requirements only apply through that specific UI layout.
Frequently Asked Questions
What\'s the difference between a page layout and a Lightning record page?
Page layouts control which fields, related lists, and buttons appear and their arrangement in a fairly fixed structure; Lightning record pages (built in App Builder) offer more flexible, component-based layout control, including dynamic visibility.
Can different profiles see different page layouts for the same object?
Yes, page layout assignment is done per profile (and optionally per record type), letting different user groups see genuinely different layouts for the same object.
Why isn\'t my new field showing up on the page layout?
New fields aren't automatically added to existing page layouts — they must be manually dragged onto each relevant layout after creation.
Can I make a field required specifically on the page layout, without a validation rule?
Yes, page layouts support marking a field as required at the layout level, though this only enforces the requirement when the record is edited through that specific layout, unlike a validation rule which applies everywhere.
Can related lists be reordered or hidden per page layout?
Yes, related lists can be added, removed, reordered, and have their displayed columns customized independently per layout.
What happens to page layout assignments when I create a new record type?
A new record type requires explicit page layout assignment per profile — it doesn't automatically inherit an existing record type's layout assignments.
Can I add a custom button or link to a page layout?
Yes, custom buttons and links (which can trigger URLs, JavaScript, or Visualforce/Flow actions) can be added to the layout's button section.
Do page layouts control field-level security?
No — page layouts control visual arrangement and layout-level requiredness; actual field-level security (visible, read-only, hidden) is a separate setting that page layouts must respect, not override.
Can I preview how a page layout looks before assigning it?
Yes, the Page Layout editor includes a preview mode showing how the layout renders for a sample record before you save and assign it.
How many sections can a page layout have?
There's no strict platform limit, but usability degrades well before any technical ceiling — most well-designed layouts use 4-8 logically grouped sections.