How To Partition Confluence for Different Isolated User Groups
プラットフォームについて: Cloud および Data Center - この記事はクラウドと Data Center 両方のプラットフォームに等しく適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
It is a common case that a Confluence admin would like to partition access to their site, restricting various user groups to their corresponding spaces within Confluence. This is especially true if you have opened up your instance to external groups of users such as customers, partners, or public (anonymous) users.
This how-to will explain the steps needed to both separate project access, while granting read-only access to particular groups working within a project. The example is written in context of granting access to various client groups.
Please be aware isolated users will still be able to mention and search for other users in other isolated groups.
First, a quick review of Confluence permissions:
Confluence supports three levels of permissions:
- Global permissions control who has access to the site as a whole, as well which users have global administrator or system administrator permissions.
- Space permissions control who has access view a space's content, but also perform content-specific actions within that space.
- Page restrictions control who has read or write access to an individual page. Any child pages underneath it inherit the set restrictions.
You can read a full overview of Confluence security here.
We'll assume here that a Confluence Administrator has already:
- Created the users in Confluence.
- Populated these users into client or team-specific groups (i.e. all users from 'Company A' are grouped into the 'Client A' group)
- Granted these groups Confluence access (via the Confluence 'Can Use' global permission).
Give groups access to only specific spaces:
- For a given space's permissions, ensure that the relevant group has the 'View' permission enabled. See Assigning Space Permissions to Groups.
Note: The View space permission determines whether a user or group access to the space as a whole. Users who do not have 'View' permissions to the space will not see the space via the Confluence space directory, and will not be able to access pages in the space linked to from other locations. - Optionally, enable 'Add' or 'Delete' comments permissions as well. Though users won't be able to edit or create page content itself, commenting can help encourage their active participation on pages.
- Add additional admin/internal groups to the space permissions to ensure that internal users can also view the project.
- Enable additional add/delete permissions (such as Add/Delete Pages) to these admin/internal groups to grant them page editing capabilities.