The pattern: identify the dominant user population, set the default to match their preference, let per-user override handle minority preferences. The cost is minimal; the user-experience impact compounds across thousands of daily sessions.
- Survey the user population on density preference
Quick survey of representative users from each role. Sales reps, support agents, marketing ops, executives. The data drives the default decision.
- Open Setup, User Interface, Density Settings
The configuration is a single radio button choice between Comfy and Compact.
- Set the org-wide default to match the dominant population
Comfy for sales-rep-dominated orgs, Compact for service-agent-dominated orgs. When unsure, default to Comfy for accessibility.
- Communicate the per-user override path to users
View > Display Density in the user settings menu. Users who prefer the non-default option need to know how to switch.
- Test on representative devices (laptop, large monitor, tablet)
Density renders differently per screen size. Confirm the choice works across the org's actual device mix.
- Document the choice and the rationale
Admin documentation. Future admins should understand why the org defaulted to Comfy or Compact.
- Audit annually as user population evolves
User-population shifts may change the right default. The annual audit catches the drift.
Generous spacing, easier to read, better for accessibility, common for sales-rep orgs.
Tighter spacing, more data per screen, common for service-agent orgs.
Each user can pick their preference through View > Display Density.
Salesforce Mobile App ignores Density Settings; uses touch-optimized density.
Review as user population evolves; the right default can shift over years.
- Per-user overrides persist across org-wide default changes. Users who customized keep their preference; only new users and uncustomized users see the new default.
- Density Settings affects desktop only. The Salesforce Mobile App uses its own density independent of this setting.
- Comfy is more accessible than Compact. Orgs subject to accessibility compliance should default to Comfy unless there is a strong reason otherwise.
- Switching the org-wide default does not retroactively change customized users. Communication is needed if you want all users to experience the new default.
- The setting is low-traffic and easy to forget. The annual audit cadence catches drift between the configured default and current user population.
Keep the related term in your library so you can find this topic again.