Layouts can be tied to security groups, individuals, or made “public” so any user can pick them. Choosing the right sharing model keeps the layout library manageable.
Sharing Models
- Per-group default: Layout used automatically for every user in that group. Most common — sales reps all get the sales layout.
- Per-group available: Members of the group can pick this layout from a dropdown, but the default may be something else.
- Personal: One specific user's customisation; nobody else can use it.
- Public: Available to any user regardless of group.
Default Resolution
When a user opens a record, the platform looks up which layout to use:
- User's manually-pinned layout (from their own “Set as default” action).
- Personal layouts assigned to this user.
- Default for the user's primary security group.
- Platform-wide fallback default.
Worked Examples
- Multi-team CRM: Sales group default = Sales view; Support group default = Support view; Finance group default = Finance view. Users in multiple groups can switch between them.
- Personal customisation: One particularly visual sales rep creates a personal layout with extra charts; only she sees it.
- Mobile layouts: A “Mobile” layout marked public; any user accessing from a small screen gets it automatically (via device detection).
- Compliance audit view: A read-only “Audit” layout marked public, available to auditors when investigation is in progress.
Tip: Don't proliferate layouts. Each new one is something to maintain. Aim for a small handful (3-5) of well-designed layouts rather than dozens of slight variations.