You are here:
Permission Set Group Considerations
When working with permission set groups, keep these behaviors in mind.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Contact Manager, Group, Essentials, Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions |
General
- You can add up to 100 permission sets to a permission set group.
- When a permission set is part of a group, you can still assign the individual permission set, apart from the permission set group, to specified users as needed.
- When viewing permission set groups in a list view, no actions are available in the list view dropdown menu.
- If you include session-based permission sets in a permission set group, the permissions in them do not require session-based activation for users assigned to the group.
- Permissions in permission set groups are calculated immediately when you change a custom permission set contained in the permission set group. Whenever you add, delete, or edit a custom permission set in the group, a calculation is applied to ensure the correct aggregation of permissions. Permission changes for Salesforce-owned standard permission sets that are added to permission set groups are calculated daily.
- If done during the deployment phase, an update to a permission set group triggers a recalculation. To test assignments, exclude changes to permission set groups in the deploy phase. Instead, add permission sets and user assignments to permission set groups in your test phase, which doesn’t trigger a recalculation.
- Use permission sets instead of permission set groups to assign permissions to test users in Apex tests. Permission set groups can be recalculated when you deploy your Apex code, in which case the test users aren’t assigned the permissions included in the permission set groups.
- You can create user access policies to more efficiently manage users' assignments to permission sets and permission set groups. For more information, see User Access Policies.
Performance
- If your org has many permission sets, using permission set groups can help improve performance.
- For better performance, we recommend assigning users permission set groups instead of many individual permission sets. This recommendation is especially important when structuring permission assignments for a large number of users, because you can experience issues if you assign many users to the same multiple permission sets.
- Permission set group recalculation can time out or take a long time to complete due to certain factors, such as if the included permission sets are complex or don’t have a required license. For more info and suggested fixes, see Permission Set Group Status and Recalculation.
Deletion
- Before you delete a permission set group, you must remove all user assignments.
- When you delete a permission set group, the individual permission sets included in the group aren’t deleted.
- You can’t delete Salesforce-provided standard permission set groups. You can only delete custom permission set groups.
- Permission set groups from managed packages can’t be deleted in subscriber orgs. To remove a permission set group from an installed managed package, you must first uninstall the package. For more information, see Permission Set Groups from Managed Packages.
- Before you delete a permission set group, verify that it isn’t referenced in Apex code, flows, or other customizations. References to a deleted permission set group can cause errors.
- Don’t delete a permission set group when its status is Updating. Deletion during recalculation can cause issues.
Did this article solve your issue?
Let us know so we can improve!
