A surprisingly common confusion: in Lightning Experience, what a user actually sees is the result of four different layout systems collaborating. Knowing how they layer is what lets you fix UI complaints accurately.
- Lightning Record Page (built in Lightning App Builder) — the top-level canvas for a record. It defines the page composition: the highlights panel at top, what tabs/accordions exist on each side, which custom components appear (path, knowledge, related lists, custom LWCs). Assigned by App + Record Type + Profile.
- Page Layout — controls the Details tab inside the Lightning Record Page when Dynamic Forms is NOT enabled. Also controls Quick Actions ("Mobile and Lightning Actions" section) and Related Lists. Page Layouts are still required even if Dynamic Forms is enabled.
- Dynamic Forms (a Lightning Record Page enhancement) — replaces the Page Layout's Details-tab field rendering with App Builder-driven component-by-component placement. Adds conditional visibility per field. Doesn't replace the rest of the Page Layout's responsibilities (related lists, mobile/lightning actions).
- Compact Layout — defines the highlights panel fields (the prominent record-header info at the top of the page) AND what shows in mobile/list views. Per object + record type.
A user reporting "I can't see this field" requires you to ask: which page area? If:
- Highlights panel at top -> fix Compact Layout.
- Details tab fields -> fix Page Layout (or Dynamic Forms if enabled).
- Right sidebar / a tab / a related list -> fix the Lightning Record Page.
- Quick Actions in the highlights panel -> fix Page Layout's "Mobile and Lightning Actions" section, or the Actions component on the Lightning Record Page.
How they're assigned:
- Lightning Record Page: by App, then Record Type, then Profile, in priority order.
- Page Layout: by Profile + Record Type.
- Compact Layout: by Record Type.
- Dynamic Forms: defined inside the Lightning Record Page itself.
This stack is messy because it evolved over years. Most modern rollouts converge on: minimal Page Layout (just for actions and related lists), full Dynamic Forms in the Lightning Record Page, distinct Compact Layouts per record type. That keeps configuration in one place (App Builder) and avoids hunting through Page Layouts.