Editing a Page Layout is one of the most-frequent admin tasks. Most Page Layout changes are small (add a new field, reorder a section), but the cumulative impact of these changes is large because every user sees them immediately on next page load.
- Open Setup and navigate to the Page Layouts for the object
Setup > Object Manager > select the object > Page Layouts. The list shows every Page Layout on the object, with the number of users assigned to each one.
- Open the Page Layout you want to edit
Click the layout name to open the layout editor. The editor shows a palette of available fields at the top and the live layout below.
- Add or rearrange fields
Drag fields from the palette to the layout. Drag fields within the layout to reorder them. Drag sections to add new sections or reorganize the page structure.
- Set Required and Read-Only flags
Hover over a field in the layout to surface the wrench icon, then toggle Required and Read-Only as needed. Required prevents save when blank; Read-Only prevents UI edits.
- Configure Related Lists and Actions
Scroll to the Related Lists section and add or remove the child objects that should appear. Scroll to the Mobile and Lightning Actions section and configure the Quick Actions and global actions.
- Save and assign
Click Save. Then go to Page Layout Assignment to confirm which Profile and Record Type combinations use this layout; assign explicitly if needed.
- Test with a representative user
Log in as a user assigned to this Page Layout (or use Login As) and confirm the layout renders correctly. New fields, required fields, and removed sections all show up at this step.
Set on Page Layout, validated on save. Different from Validation Rules; both fire on save but Required is simpler and surfaces a clearer error.
Locks the field on the UI; can still be set programmatically through Flow or Apex. Useful for system-of-record fields that downstream automation maintains.
- Page Layout Required is layered on top of field-level security. A field hidden through FLS but marked Required on Page Layout produces an unsaveable record; ensure FLS aligns with Page Layout requirements.
- Page Layouts assigned per Profile per Record Type. Forgetting to assign a new layout means users default to the Master layout, which is usually not what you want.
- Lightning Record Pages can override Page Layout behavior in Lightning Experience. If your Lightning Record Page does not include the Record Detail component, the Page Layout's field configuration is invisible to users.
- Compact Layout is separate from Page Layout. Editing the Page Layout does not change the highlight panel at the top of the record page; that lives on Compact Layout.