You are here:
Public Group Considerations
For organizations with a large number of users, consider these tips when creating public groups to optimize performance.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions |
- Create a group when at least a few users need the same access.
- Create a group for members who don’t need to frequently move in or out of the groups.
- If your group contains more than 10,000 members, you can experience performance issues or group members being deleted when updating membership on the group's Edit or Create pages. To prevent these issues, adjust group membership using the public group's access summary, user access policies, or the GroupMember API. You can also contact Salesforce Customer Support to enable the modified Group Setup interface.
- Avoid creating groups within groups that result in more than five levels of nesting.
- Enable automatic access to records using role hierarchies for public groups by selecting Grant Access Using Hierarchies when creating the group. However, don’t use this option if you’re creating a public group with All Internal Users as members. For performance reasons, it's also recommended that you keep this option disabled if users above the public group members don’t need access to records shared with the group.
- In Salesforce orgs created before February 8, 2024 that enabled digital experiences before Winter ’26, all Roles and Subordinates members in groups are converted to Roles, Internal and Portal Subordinates members. Review public groups that contain Roles, Internal and Portal Subordinates members, and replace them with Role and Internal Subordinates as required.
- You can’t include high-volume community or site users in public groups.
Did this article solve your issue?
Let us know so we can improve!
