--- schema_version: "1" id: cb4452a2acf8427c77229f3cb86888cd96031ca7912a7d1afdf70548bd28de12 title: Create Public Groups for Knowledge collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/knowledge_setup_assign_users.md canonical_url: https://help.salesforce.com/s/articleView?id=service.knowledge_setup_assign_users.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 154a2794e85964f5e3be92240cc3f5e2fcb673af6f1f98fb57460ba413c07d43 description: Salesforce Knowledge uses public groups as a way to assign users to specific tasks related to articles. When you assign article actions to a public group, you can grant users in that group the ability to do things like publish articles with a specified validation status. Public groups are also used in approval processes to manage the publishing workflow. products: - Service Cloud release: "264" --- # Create Public Groups for Knowledge Salesforce Knowledge uses public groups as a way to assign users to specific tasks related to articles. When you assign article actions to a public group, you can grant users in that group the ability to do things like publish articles with a specified validation status. Public groups are also used in approval processes to manage the publishing workflow. ### Required Editions
Available in Salesforce Classic. View supported editions.
User Permissions Needed
To create or edit a public group: Manage Users
To create or edit another user’s personal group: Manage Users
For example, when a member of the [Candidate](https://help.salesforce.com/s/articleView?id=service.knowledge_setup_users.htm&release=264.0.0&type=5) public group submits an article with the status Work in Progress for approval, it is automatically approved and published. If the same service rep submits an article with Validated Internal status, it moves to the Publishing External queue to be reviewed before being published. 1. From Setup, enter Public Groups in the Quick Find box, then select **Public Groups**. 2. Click **New**, or click **Edit** next to the group you want to edit. 3. Enter the following information:
Field Description
Label The name used to refer to the group in any user interface pages.
Group Name (public groups only) The unique name used by the API and managed packages.
Grant Access Using Hierarchies (public groups only)

To allow automatic access to records using your role hierarchies, select Grant Access Using Hierarchies. When selected, any records shared with users in this group are also shared with users higher in the hierarchy.

Deselect Grant Access Using Hierarchies if you're creating a public group with All Internal Users as members, which optimizes performance for sharing records with groups.

If Grant Access Using Hierarchies is deselected, users that are higher in the role hierarchy don't receive automatic access. However, some users can still access records they don't own. Examples of such users include users with the View All Records and Modify All Records object permissions and the View All Data and Modify All Data system permissions.
Search

From the Search dropdown, select the type of member to add. If you don't see the member you want to add, enter keywords in the search box and click Find.

For account owners to see child records owned by high-volume Experience Cloud site users, they must be members of any share groups with access to the site users' data.
Selected Members Select members from the Available Members box, and click Add to add them to the group.
Selected Delegated Groups In this list, specify any delegated administration groups whose members can add or remove members from this public group. Select groups from the Available Delegated Groups box, and then click Add. This list appears only in public groups.
4. Click **Save**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/images/icon_note.png) Note When you edit groups, sharing rules are automatically reevaluated to add or remove access as needed. If these changes affect too many records at once, a message appears warning that the sharing rules aren’t automatically reevaluated, and you must manually recalculate them. Now assign only the necessary actions to your groups so the selected members can perform their tasks while keeping the integrity of your knowledge base. #### See Also - [Create Workflow Actions for Knowledge](https://help.salesforce.com/s/articleView?id=service.knowledge_actions_create.htm&release=264.0.0&type=5 "Knowledge actions are templates that link a workflow action to an article type. When knowledge actions are enabled, you can use them to link article types to specific workflow article actions, such as publishing. For example, if you want each FAQ to publish as a new version when it completes the approval process, you can create a knowledge action that links an FAQ article to the Publish as New action. Then, when you create an approval process for FAQs, select the new Knowledge action.") - [Assign Article Actions to Public Groups](https://help.salesforce.com/s/articleView?id=service.knowledge_article_actions.htm&release=264.0.0&type=5 "Article actions let support reps participate in the article publishing process. By default, all article actions are assigned to users with the “Manage Articles” user permission. Support reps can complete an action as long as they have the correct article type permission. You can control article action access by assigning public groups to article actions and adding support reps the relevant public groups. To further restrict actions like publishing, you can create approval processes that allow support reps to publish only those articles that have specific validation statuses. For example, many contributors can write many articles but you can create an approval process so no articles are published until they are reviewed and validated by a qualified author.") - [Classic Knowledge User Access](https://help.salesforce.com/s/articleView?id=service.knowledge_setup_users.htm&release=264.0.0&type=5 "Specify which support reps in your company are Classic Knowledge users and give them access to article actions. Create user profiles with the user permissions they need, and then assign them to these profiles.") - [Salesforce Knowledge Help and Resources](https://help.salesforce.com/s/articleView?id=service.knowledge_map.htm&release=264.0.0&type=5 "Find the information you need about Salesforce Knowledge. Explore help documentation, developer documentation, and Trailhead modules.")