The pattern: identify low-frequency sections, set them default-collapsed, leave high-frequency sections default-expanded, watch usage. The cost is minimal; the readability gain is meaningful for any page with more than 5 to 7 sections.
- List the sections on the page
Open the Lightning Record Page in App Builder. Count the sections. Pages with fewer than 5 sections probably do not need collapsible defaults; pages with 8+ sections benefit a lot.
- Identify the high-frequency sections users always need
The top one or two sections (Account Information, Opportunity Details) usually stay default-expanded. Everything else is candidate for default-collapsed.
- Mark low-frequency sections as default-collapsed
Click into each section, toggle Default Collapsed. System Information, Audit Fields, archival sections are typical candidates.
- Pair with conditional visibility where applicable
Sections that should only appear under specific conditions get conditional visibility instead of (or in addition to) collapsible. Cleaner than collapsing always-irrelevant sections.
- Test on mobile viewport
Open the page on a phone-sized window or actual mobile device. Confirm the default-collapsed state matches what mobile users want to see first.
- Publish and gather feedback
Activate the page. Watch for user complaints about hidden information; the defaults are the admin's hypothesis and users will tell you if you got it wrong.
- Refine quarterly based on usage signals
Lightning Usage Reports show which components users interact with most. Sections users always expand should become default-expanded; sections users never expand should be considered for conditional visibility or removal.
Per-section setting; the admin's hypothesis about what most users want to see on load.
Show or hide entire sections based on field values. Better than collapsible for always-or-never information.
Three information-density patterns. Pick based on the user workflow.
Mobile users see the same collapsible defaults unless a separate mobile page is built. Most teams use one shared layout.
Collapse state persists per user per section. Users control their own view across visits.
- Over-using default-collapsed hides information users need on every visit. Reps complain about repeated expansion clicks; recalibrate based on real usage.
- Collapsed sections still render in the DOM. Performance-sensitive pages should use conditional visibility for heavy components, not just collapse.
- Default state applies only to users who have not personally adjusted. Tenured users keep their settings; admin defaults shift only for new or unchanged users.
- Mobile and desktop share the same collapsible defaults unless separate mobile pages are built. A default that works on desktop may feel busy on mobile.
- Collapsible is sometimes used as a substitute for proper page design. Pages with too many sections need restructuring, not just collapsing.