Admin Console hierarchical settings at org default and profile levels
Key Takeaway
A profile-level configuration takes precedence over the org default for that profile's users, and you can't delete it from the UI. To give those users the org default's values, update the profile-level configuration to match. For Mobile Sync Settings, then create a metadata cache so the changes reach the mobile app.
Several Life Sciences Cloud Admin Console configurations use a hierarchical framework. You define a setting once at the org default level. Then you override it for specific user profiles whose users need different behavior. To configure these settings correctly, you need to know which level wins and which actions you can't undo from the UI.
Org default and profile levels
A configuration that supports the hierarchical framework can be set at two levels.
| Level | Applies to |
|---|---|
| Org default | All users, unless a profile-level configuration overrides it |
| User profile | Only users assigned to that profile |
The profile level wins. When a profile-level configuration exists, it takes precedence over the org default. The Life Sciences Cloud mobile app also uses the profile-level configuration instead of the org default for users in that profile. Think of the org default as the house rule and a profile-level configuration as a standing exception for one group.
The intended pattern is to set the org default for the behavior most users need. Then add profile-level configurations only for profiles that must behave differently, such as Field Sales Representatives or Medical Science Liaisons.
Jordan manages a Life Sciences Cloud org with 300 users. On the Consent Administration page, Jordan sets the org default for what most of those users need. Fifteen users on a Market Access Manager profile need different behavior, so Jordan adds a profile-level configuration for that profile. Those fifteen users get the profile-level values, including in the Life Sciences Cloud mobile app. The other 285 users get the org default.