User Interface
Assembling pages
Lightning App Builder builds record, home, and app pages, assigned by app, record type, and profile or permission set. Components come from the standard library, AppExchange, or custom Lightning Web Components. A Lightning app groups tabs and defines navigation; the utility bar adds persistent tools to console apps. Layouts are separate artifacts: page layouts drive fields and related lists in the detail area, compact layouts drive the highlights panel, mobile cards, and recent items, and search layouts drive columns in lookup dialogs.
Modern tools
Dynamic Forms move field and section configuration off the page layout onto the record page, enabling per-component visibility rules. Dynamic Actions do the same for buttons, and the dynamic highlights panel replaces the compact layout for key fields. These require an upgraded record page and are not available for every object.
Traps
- Thinking a page layout secures a field. It does not; field-level security does.
- Marking a field required on the page layout and assuming the API enforces it. It does not.
- Forgetting that Lightning page assignment by app, record type, and profile decides what a user actually sees.
- Expecting compact layout edits to change the record detail area.
- Adding a component to a page and never assigning the page, so users still see the default.
Rule of thumb
Where does it show? Page layout for detail, compact layout for highlights, search layout for lookups. Who sees it? Field-level security plus page and component visibility rules.