Several Life Sciences Cloud Admin Console configurations use a hierarchical framework, so
you can define settings at the org default level or override them for specific user profiles.
Review how precedence works and the current considerations before you plan your
configuration.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Life
Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the
Life Sciences Customer Engagement managed package.
How Precedence Works
When a configuration supports the hierarchical framework, you can set it at two levels:
Org default: Applies to all users unless a profile-level configuration overrides
it.
User profile: Applies to users assigned to that profile and takes precedence over
the org default configuration.
If a profile-level configuration exists, the Life Sciences Cloud mobile app uses it instead
of the org default configuration for users in that profile.
Considerations
These considerations apply to all Admin Console configurations that use the hierarchical
framework,.
Hierarchical configurations support only creating and updating (upsert). After you set a
configuration at a level, you can change its values, but you can't delete the
configuration from the UI.
Because a profile-level configuration takes precedence over the org default, you can't
remove a profile-level configuration to make users fall back to the org default value
from the UI. Instead, update the profile-level configuration to match the intended
values.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.