Organizing your readers into groups can streamline content access management and ensure each reader has the appropriate permissions to view specific articles. Reader groups in Document360 allow you to efficiently control which sections of your knowledge base are accessible to different readers.
What you can do with reader groups
| Task | What it does |
|---|---|
| Create a reader group | Create a new group, set content access, and associate readers |
| Edit a reader group | Update group name, content access, and associated readers |
| Delete a reader group | Remove a group without deleting the individual reader accounts |
| Export a reader group | Download the list of readers in a group as a CSV file |
Before you begin
- Reader groups are only available when your project's reader access is set to Private or Mixed.
- Only users with the Admin or Owner portal role, or a custom role with Manage user permission, can create, edit, or delete reader groups.
FAQ
What happens if I assign content access to a reader at both the individual and reader group levels?
When content access is assigned to a reader at individual and group levels, individual-level permissions will take precedence.
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 will still have access to the entire knowledge base.
Can I restrict a specific reader group from viewing only private content and hide public content from them?
No, it is not possible to hide public content from any reader groups. By default, public content is visible to all users. If you want certain content to be visible only to specific readers, you need to make that content private and assign it to the appropriate reader group using the Content access feature.