Adding a field to the Detail section is one of the most common admin tasks. The path depends on whether the record page uses a Page Layout or Dynamic Forms; both routes get you there in under five minutes.
- Identify the record page type
Open the object's record page in Setup or in the App Builder. Look for the Detail Section component. If it references a Page Layout name, you are on the classic layout path. If it uses individual Field components for each field, you are on Dynamic Forms.
- For Page Layouts: edit the assigned layout
Setup, then Object Manager, then the object, then Page Layouts, then the layout name. Drag the field from the palette onto a section. Save.
- For Dynamic Forms: edit the Lightning record page
Setup, then Lightning App Builder, then open the record page. Drag a Field component onto the canvas. Pick the field. Set any visibility rules. Save and activate.
- Confirm field-level security
The field needs Read access on the user's profile or permission set for it to appear. Setup, then Object Manager, then the object, then the field, then Set Field-Level Security, then check the relevant profiles.
- Test as the affected user
Use Login As or test with an account that has the relevant profile. Open a record's Detail page and confirm the field renders with the right value and the right editability.
- Repeat for multiple page layouts if applicable
Many orgs assign different page layouts per profile or record type. Audit each layout that uses the Detail Section, or migrate to Dynamic Forms to consolidate.
Single layout drives the Detail section. Each profile and record type gets one assigned layout. Common in mature orgs.
Field-by-field placement on the record page. Each field has its own visibility rules. The recommended modern approach.
The data-model meaning of detail: a child record whose existence and sharing depend on a master.
The looser alternative to master-detail. The detail concept does not apply to lookups.
- Page layouts and Dynamic Forms are mutually exclusive on a given record page. If you migrate to Dynamic Forms, the page layout no longer drives the Detail section. Older page layouts still exist but are bypassed.
- Field-level security gates visibility everywhere. Adding a field to the layout does nothing if the user''s profile lacks Read on the field.
- Master-detail''s cascading delete cannot be turned off. If you need parent deletion to leave children intact, use a lookup with a delete-cascade-blocked configuration, not master-detail.
- Detail records inherit the master''s owner and cannot be assigned a different one. Roll-up summaries depend on this for performance.