Permission Set Group Muting Dependencies

Note Users outside of the permission set group that are assigned directly to the included permission sets remain unaffected by muting. The muting permission set only affect the related permission set group’s users.

Muting permissions in a permission set group offers you granular control over user permission assignments, but keep in mind the impact on dependent permissions. The table details object permission dependencies.

When muting user permissions, pay attention to the permission change confirmation message when you save your changes for permission dependencies. For example, if you mute the Activate Contracts permission, then the Delete Activated Contracts permissions is muted as well.

Muting object permissions can also affect user permissions. For example, one of the permission sets in your permission set group includes the Activate Orders user permission. Because Activate Orders requires Read and Edit object permissions on Orders, these object permissions are enabled automatically. If you mute the Edit permission, the Activate Orders user permission is muted as a result.

Note If you mute the Modify All Data or View All Data user permissions, included object permissions aren’t affected. For example, a permission set has the Modify All Data permission and Create, Read, Edit, and Delete permissions for Accounts. You add the permission set to a permission set group and create a muting permission set that has only Modify All Data muted. As a result, Modify All Data is muted, but the Account object permissions stay enabled. If you don’t want users in the permission set group to have access to objects, you must also explicitly include the specific object permissions in the muting permission set.

Example

For example, the Sales Staff Users permission set group contains three permission sets and a muting permission set. The muting permission set mutes the Delete permission on Accounts and Opportunities.

When you mute Delete on an object, Modify All Records is automatically muted (even if you didn’t enable it for that object). Modify All Records becomes disabled because it depends on full object access, which is no longer available when you mute Delete.

Similarly, if you mute Read on the object, then Create, Edit, Delete, View All Records, and Modify All Records are muted. If you can’t read object data, then you can’t perform actions such as delete on it.