Customizing a Detail View means editing the Lightning Record Page in Lightning App Builder. The page composes components for a specific object's record view; activation rules decide which users see which page.
- Open Lightning App Builder
Setup, then Lightning App Builder. Find the existing Lightning Record Page for the object, or click New to create one. Pick Record Page as the type.
- Review the canvas
The canvas shows the components currently on the Detail View. Highlights Panel at the top, the Detail Section or Dynamic Forms components in the body, Related Lists and Activity timeline in the right or bottom regions.
- Add, remove, or reorder components
Drag Lightning components from the left palette: standard (Detail Section, Related Lists, Path, Activity, Chatter) and custom (LWC or Aura). Reorder by dragging within the canvas. Each component has its own properties on the right rail.
- Configure component properties
Click a component to see its properties. For the Detail Section, pick the page layout or switch to Dynamic Forms. For Related Lists, choose which lists to show. For custom components, set the API attributes.
- Set component visibility rules
Each component supports filters: show only when a record matches certain criteria, or only for users in certain profiles. Use this to surface special components on premium accounts or hide internal-only sections from community users.
- Save and activate
Click Save. Click Activation. Set the page as the org default, a profile default, or an app-and-record-type assignment. The new Detail View takes effect immediately for matching users.
The Lightning Record Page editor. Drag components, set properties, configure activation rules.
Replace the single Detail Section with field-by-field placement. Per-field visibility rules and column control.
The legacy way to drive a Detail View. Still works in Lightning when the Detail Section component points to a layout.
Drives the fields shown in the top strip of the Detail View. Set per object in Object Manager.
- Activation order matters: app-and-record-type, then profile, then org default. The most specific match wins, so a profile-specific assignment overrides the org default for that profile.
- Dynamic Forms and the Detail Section component are mutually exclusive on a single page. You either drive fields through a page layout or place them as individual Field components, not both.
- Custom Lightning components on a Detail View can slow page render. Profile with the Lightning Page Performance Profiler before adding more than five custom components.
- Removing a Related List from the Detail View hides it but does not delete the relationship or the records. The child records remain reachable through other Detail Views or list views.