All docs pages (49)

Permission Dependencies

Which Salesforce permissions need others: what a grant must include, what a removal takes with it, and how muting reverses the chain.

Updated 2026-11-10

Permission dependencies

Salesforce won't save some permissions without others. Edit needs Read, Delete needs Edit, and Modify All needs View All, Delete and Edit. This guide lists those rules.

When you save a profile or permission set in Setup, Salesforce turns on what your change needs for you. Changes made through the API are not fixed for you: a change that breaks a rule is refused. Salesforce's help says that for API updates "you must manually fix broken permission dependencies". Tools that write permissions through the API, including SFDC Police, have to follow these rules themselves.

The object and field rules below were checked against a live org in November 2026. The quoted messages are the errors Salesforce returned.

Object permissions

To grantYou also needWhat Salesforce says otherwise
ReadNothing
CreateRead"Permission Create Lead depends on permission(s): Read Lead"
EditRead"Permission Edit Lead depends on permission(s): Read Lead"
DeleteEdit, and so Read"Permission Delete Lead depends on permission(s): Edit Lead"
View All RecordsRead"Permission View All Lead depends on permission(s): Read Lead"
Modify All RecordsView All Records, Delete and Edit, and so Read"Permission Modify All Lead depends on permission(s): View All Lead", and without Edit and Delete: "…depends on permission(s): Delete Lead; … Edit Lead"
View All FieldsReadSalesforce Help: the user "must also have at least Read permission"

Removing a permission takes away everything that needs it:

To removeAlso remove
ReadCreate, Edit, Delete, View All, Modify All, View All Fields
EditDelete, Modify All
DeleteModify All
View All RecordsModify All

Field permissions

Field Edit needs field Read. Granting Edit without Read is refused with "Read permission is required for: Lead.Industry". Removing Read also removes Edit.

Muting permission sets

A muting permission set removes permissions from its own permission set group, so the chain runs the other way. To mute a permission, first mute everything that depends on it. Muting Delete before Modify All is refused with "To mute Delete, first mute Modify All Records."

Master-detail objects

A child object's permissions need permissions on its parent (Salesforce Help, Object Permissions):

If the child object hasThe parent object needs
Modify All Records or View All RecordsView All Records
View All Records or ReadRead

Everything else: your org's own list

Many more dependencies exist between system permissions and objects. For example, Export Reports needs Run Reports, Mass Email needs Send Email, Import Personal Contacts needs Create on Account, and Modify All Data needs View All Data, View Setup and permissions on many objects. Which rules apply depends on your org's edition, features and installed packages.

Salesforce lists them in the PermissionDependency object of the Tooling API. One org we checked had more than 2,000 rows. To see what a permission needs in your org, run this with the Tooling API, for example in SFDC Police's SOQL Builder with its Tooling API toggle on:

SELECT Permission, PermissionType, RequiredPermission, RequiredPermissionType
FROM PermissionDependency
WHERE Permission = 'ExportReport'

Object entries look like Account<read>. The permission names are read, create, update (Edit), delete, viewAllRecords and modifyAllRecords.

Sources

Related