---
schema_version: "1"
id: a77a4473adaa4eb51113208058360be53e00a887f0bd7c804c6fadeaed9ca943
title: Public Group Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/user_groups_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.user_groups_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3586b95f83730fa223443e5bcc296580cb32ff96422d57c03d52c265875a9194
description: For organizations with a large number of users, consider these tips when creating public groups to optimize performance.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Public Group Considerations

For organizations with a large number of users, consider these tips when creating public groups to optimize performance.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, <strong>Developer</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

- 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.

#### See Also

- [Public and Personal Groups](https://help.salesforce.com/s/articleView?id=platform.user_groups.htm&release=264.0.0&type=5 "A group consists of a set of users. A group can contain individual users, other groups, or the users in a particular role or territory. It can also contain the users in a particular role or territory plus all the users below that role or territory in the hierarchy.")
- [_Designing Record Access for Enterprise Scale_: Group Membership Locking](https://developer.salesforce.com/docs/atlas.en-us.draes.meta/draes/draes_group_membership_locking.htm)