A Page Layout in Salesforce controls which fields, sections, related lists, and actions appear on a record and how they are arranged. Admins assign Page Layouts by Profile. For objects that use Record Types, the combination of a user’s Profile and the record’s Record Type determines which Page Layout they see. This allows users with different Profiles to see different layouts for the same record.
PRACTICAL EXAMPLE
Sales reps and support agents both work with Account records. The admin creates a “Sales Account Layout” with the Opportunities related list and a “Support Account Layout” with the Cases related list. The admin assigns each layout to the corresponding Profile, so each team sees the related information most relevant to its work.
Quick Facts
-
Assigned by Profile, and by Record Type when used: which layout a user sees depends on their Profile. If the object uses Record Types, it depends on the combination of Profile and Record Type.
-
A layout does nothing until it is assigned: Creating a Page Layout doesn’t automatically make it visible to users. You must assign it to the appropriate profiles. If an object uses record types, Salesforce determines the displayed layout based on the user’s profile and record type.
-
Fields, Related Lists, and Mobile & Lightning Actions: Fields are organized into sections on the page layout. Authoring actions added to the Salesforce Mobile and Lightning Experience Actions section appear in the highlights panel on record pages in Lightning Experience and in the Salesforce mobile app.
-
One object, many layouts: an object can have several Page Layouts, for example separate layouts for readers and authors.
-
Lightning Record Pages are a separate tool: Lightning record pages are built in Lightning App Builder, where admins arrange and customize components on the page. This is separate from the page layout editor in Object Manager, which controls the fields, related lists, and actions that the page layout supplies.
-
Some features still read the Page Layout: On pages built with Dynamic Forms, the fields for viewing, creating, editing, and cloning generally come from the Lightning page. For objects that Dynamic Forms does not support, such as Products, Events, and Tasks, the page layout provides the fields. Fields available for inline editing in list views, key fields in a Path, and actions on standard objects also come from the page layout.
Note
A Page Layout controls what appears on a record page, not who has access to the data. Removing a field from a layout hides it on that page, but the field may still be reachable elsewhere, for example in reports or through the API. Field access is set by Field-Level Security, which is a separate setting. In Salesforce’s own Lightning Knowledge example, a field is added to the Author layout and its visibility is also limited through Field-Level Security.
FAQ
What’s the difference between a Page Layout and a Record Type in Salesforce?
A Page Layout controls what users see on a record: the fields, buttons and actions, and related lists. A Record Type controls which picklist values (and, for Opportunities, Cases, Leads, and Solutions, which business process) are available for a record. The two work together, because you can assign a different page layout to each record type and profile combination.
What’s the difference between a Page Layout and Field-Level Security in Salesforce?
A Page Layout decides which fields appear on a record page and how they are arranged. Field-Level Security is a separate setting that controls whether a user can see or edit a field. In Salesforce’s Lightning Knowledge example, a field is added to a page layout, and its visibility is set separately through Field-Level Security. For instance, the Internal Notes field is restricted to a support profile.
What’s the difference between a Page Layout and a Lightning Record Page in Salesforce?
A page layout, edited in Object Manager, controls which fields, actions, and related lists appear for a record. A Lightning Record Page, built in Lightning App Builder, controls how the page is arranged using components. With Dynamic Forms, you can place fields and sections on the Lightning Record Page as individual components and show or hide them with visibility rules. It isn’t supported for every object, so Tasks, Events, and Products still rely on the page layout.
Can different users see different Page Layouts for the same object?
Yes. The layout a user sees depends on their Profile. If the object uses Record Types, it depends on the combination of Profile and Record Type. For example, a Sales profile and a Support profile can see different layouts for the same Account record.