Editing a record's field form is the most common layout task. Here is the path for the enhanced page layout editor, which Salesforce recommends over the original editor. The steps assume Lightning Experience and an object you have permission to customize.
- Open the object's layouts
In Setup, use the Object Manager, open the object, then select Page Layouts. Click the layout you want to edit, or click New to create one based on an existing layout.
- Place fields and sections
Drag a Section element onto the form to group fields, then drag fields from the palette into it. Valid drop spots highlight in green. Set each field's Required and Read-Only properties using the wrench icon.
- Configure related lists, buttons, and actions
Scroll to the Related Lists area and add or reorder the child objects to show. Use the Buttons and Mobile and Lightning Actions sections of the palette to control which actions appear on the page.
- Save and assign the layout
Click Save, then use Page Layout Assignment to map this layout to the right profiles and record types. Repeat per record type so each audience sees the intended form.
Forces the field to be filled before saving through this form, on top of any database-level requirement.
Prevents editing the field on this form for users who would otherwise have edit access via field-level security.
Chosen separately from the Page Layout; it controls the Highlights panel fields and mobile previews per record type.
For supported objects, you can migrate the page layout fields onto the Lightning Page in App Builder for column, tab, and visibility-rule control.
- Layout Required and Read-Only are not the same as field-level security. A field hidden by field-level security never appears, no matter what the layout says.
- New profiles do not auto-inherit your layout. Until you assign a layout per record type, those users may land on a default layout that omits fields they need.
- Removing a field from the layout does not delete the data. The value stays in the database and can still be set by automation, imports, or the API.