Some object and user (app and system) permissions are dependent on each other to make
sure that assigned users have the correct access to related data and tasks. When needed,
Salesforce automatically enables dependent permissions in profiles and permission sets to grant
assigned users required object and feature access.
Required Editions
Available in: both Lightning Experience and Salesforce Classic
The available permissions and access features vary according to which edition you
have.
Whenever you save a profile or permission set, Salesforce evaluates whether dependent
permissions must be enabled as part of the current updates that you’re making or from previous
changes. For example, you previously enabled the View All Records permission for a custom
object in a permission set. You later created a master-detail field for this custom object,
making Account the parent object. Because of this relationship, the View All Records
permission must be enabled for Account as well. The next time you save this permission set,
this Account object permission must be enabled to keep these permission dependencies in
alignment and to fix the broken permission dependency.
In the enhanced profile user interface, updates that must be made to keep permission
dependencies in alignment after previous changes are surfaced for your review.
In addition, for all profile and permission set alignment changes, whenever permissions are
enabled to keep permission dependencies in alignment after previous changes, these edits are
surfaced in the Setup Audit Trail.
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.