Detail
Detail in Salesforce has two distinct meanings depending on context.
Definition
Detail in Salesforce has two distinct meanings depending on context. In data modeling, a detail is the child side of a master-detail relationship: a record whose existence depends on a master record, whose ownership and sharing are inherited from that master, and which is deleted when the master is deleted. In UI configuration, the Detail section (or Detail tab) is the area on a record page that shows the individual field values for that record, organized through a page layout or a Dynamic Forms component.
Both meanings come up frequently. Master-detail's detail records appear in roll-up summaries, share visibility with their master, and cannot be reparented without admin permission. The Detail UI section is where users see and edit the bulk of a record's fields, distinct from the Highlights Panel at the top, the Activity timeline, the Chatter feed, and the related lists. The two meanings rarely conflict in conversation, but knowing the difference saves confusion when an admin says add a field to the detail.
What detail means in Salesforce data modeling and UI
The detail record in a master-detail relationship
A master-detail relationship has two sides: the master (parent) and the detail (child). The detail record inherits sharing and ownership from its master, meaning users with read access to the master automatically get read access to the detail. Deleting the master cascades to the detail. The detail record's Owner field is read-only and tracks the master's owner. This tight coupling is what distinguishes master-detail from a regular lookup.
How detail records contribute to roll-up summaries
Roll-up summary fields on the master object aggregate values from its detail records: SUM(Amount), COUNT, MAX(CloseDate), and so on. The master recalculates the roll-up whenever a detail is inserted, updated, or deleted. This is the most common reason to choose master-detail over a regular lookup: roll-ups only work across master-detail relationships.
The Detail UI section and page layouts
On a record page, the Detail section is the largest field-display area, separate from the Highlights Panel (a few key fields at the top), the Related lists (child records), and the Chatter feed. The fields shown in the Detail section come from the assigned page layout. In Dynamic Forms (the modern Lightning approach), individual Field components replace the single Detail section, letting admins place fields with per-field visibility rules and column placement.
Classic page layouts versus Dynamic Forms
Salesforce Classic record pages use a single page layout that drives the Detail section as one rectangle. Lightning record pages can either use the same page layout (Detail Section component points to a Page Layout) or use Dynamic Forms (replace the Detail Section with individual Field components for each rendered field). Dynamic Forms unlock conditional visibility per field and more granular column control.
Detail records and the sharing model
Detail records cannot have their own sharing rules. Their visibility is entirely governed by the master's sharing. If a user can see the master, they see the detail (modulo field-level security). This makes master-detail powerful for compliance use cases: you control access at the master, and the platform enforces it on the children automatically.
Reparenting and the conversion to lookup
By default, a detail record's master cannot be changed once set: the master-detail field is read-only after insert. You can enable Allow reparenting on the master-detail field if your data model requires moving a detail to a different master. A master-detail relationship can also be converted to a regular lookup (and back) on objects that have records, but with restrictions: cumulative roll-ups and sharing semantics change with the conversion.
The detail-page URL pattern and deep linking
In Lightning, a record's Detail page is reachable at /lightning/r/ObjectApiName/RecordId/view. The view suffix is the Detail-page action; edit opens the inline edit experience. Deep linking to specific tabs or related lists adds query parameters. Knowing the URL pattern matters for help articles, support emails, and any integration that needs to direct users to a record's detail view.
How to add a field to the Detail section of a record page
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.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Detail.
- Master-Detail Relationship ConsiderationsSalesforce Help
- About Dynamic FormsSalesforce Help
- Page Layouts in Lightning ExperienceSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the Detail section of a record page?
Q2. What modern Lightning feature gives finer control over the Detail section?
Q3. What's the advantage of conditional visibility?
Discussion
Loading discussion…