--- title: "Edit reader group" slug: "edit-reader-group" description: "Edit reader groups in Document360 to update names, access levels, and manage associated accounts easily. Ensure proper permissions for effective changes." updated: 2026-10-08T09:52:12Z published: 2026-10-08T09:52:12Z canonical: "docs.document360.com/edit-reader-group" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.document360.com/llms.txt > Use this file to discover all available pages before exploring further. # Edit reader group Editing a reader group in Document360 lets you update the group's name, adjust its content access level, and add or remove associated reader accounts. Changes to a reader group apply to all readers in that group. --- ## When to edit a reader group - The group's name or description needs to be updated. - You need to change the content access level for all readers in the group. - You want to add new readers to the group or remove existing ones. --- ## Before you begin - You must have the **Admin** or **Owner** portal role, or a custom role with **Manage user** permission. --- ## How to edit a reader group 1. Navigate to **Settings** () > **Users and security** in the left navigation bar in the knowledge base portal. 2. In the left navigation pane, navigate to **Readers & groups** > **Reader groups**. 3. Hover over the desired reader group. The **Edit** () icon and **Delete** () icon appear. ![Reader groups overview page showing the edit and delete icons on hover.](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/26_Screenshot-Reader_groups-Edit_or_delete_reader_group.png) 4. Click the **Edit** () icon. The reader group detail page opens. 5. Update any of the following as needed: - **Name** — update the group name. - **Content access** — change the access level assigned to the group. - **Associated readers** — add new reader accounts to the group or remove existing ones. NOTE - This behavior applies only to projects that have migrated to inherited permissions for readers. In projects that haven't migrated yet, the category tree doesn't cascade, and you must select each category individually. - Selecting a parent category automatically selects all its categories and subcategories, shown with an **Inherited** badge. - If Block Inheritance has been applied to a specific category or subcategory, that will be excluded from the automatic selection. It appears unchecked with an **Inheritance blocked** badge, and you can manually select it to grant explicit access to that category. - The category tree only displays categories you have access to. 1. Click **Update** to save your changes. > [!NOTE] > **NOTE** When content access is assigned to a reader at both the individual level and the group level, the reader gets the highest level of access from all sources. Individual and group access are combined; neither overrides the other. --- ## Limitations | Limit | Detail | | --- | --- | | Maximum readers per group | 5000 readers | | Individual vs group access | When a reader has access assigned at both the individual level and through the group, the reader gets the highest level of access from both. Neither overrides the other. | --- ## Best practices - Review the associated readers list when changing a group's content access level to confirm all readers in the group should receive the new access level. - If only a subset of readers in the group needs a different access level, manage those exceptions at the individual reader level rather than splitting the group. --- ## FAQ **What happens if I assign content access to a reader at both the individual and reader group levels?** The reader gets the highest level of access from their individual setting and all the reader groups they belong to. Individual and group access are combined; neither overrides the other. For example, if a reader is granted access to the entire knowledge base at the individual level but only to a specific category as part of a reader group, they have access to the entire knowledge base.