Configuration profiles
Give a role or a group different settings without changing the base configuration.
Most fields in Configuration can carry a
value in a profile: a set of values scoped to a role or a group that
beats the base for those people and leaves everyone else on the base.
This is how the power-users group gets a 200 MB upload cap, or the
beta group sees an extra model, without touching the default.
The panel calls these profiles and profile values; the scope selector lists them next to Base configuration.
Scopes and priority
| Scope | Applies to | Priority when created |
|---|---|---|
| Base configuration | everyone | |
| Role profile | people who hold the role | 10 |
| Group profile | people in the group | 20 |
| User profile | one person | 100 |
Higher priority wins, so a group beats a role and a user beats both. The numbers are defaults: on Access, drag items to reorder the priority and confirm with Save priority order. Two groups a person belongs to resolve the same way, by priority.
User profiles are listed if they exist, but the page that creates them, Users, is not enabled in the shipped panel, so in practice you work with roles and groups.
Add a profile
Import YAML can also target a profile: choose it as the import target and give it a priority.
An example
Upload size per conversation:
- Base configuration: 50 MB.
- Group
power-users, priority 20: 200 MB. - Role
RESEARCH, priority 10: 100 MB.
A member of power-users who also holds RESEARCH gets 200 MB; someone
with the role alone gets 100 MB; everyone else 50 MB. Reorder the
priorities on Access and the outcome changes with them.
Why does this person see this value?
Open the field in Configuration and click Profiles next to it. The popover lists every scope that sets the field, its value, and which one is inherited. That is the answer, without working the cascade out by hand.
Remove a profile value
Switch to the profile, clear the field or choose Remove profile value, and save. Delete configuration on the scope removes the whole profile. Both take effect on the next request.
Which scope to use
- A role for defaults that should follow people as their job changes.
- A group for a known set of people who need more, or less, than the default.
- If you keep making the same exception for one person after another, make a group and set it once.