What are Confluence's roles?
This article describes Confluence’s new role-based access control beta feature.
When roles are enabled in your Confluence instance, you can find them by going to Confluence settings > Security > Space permissions > Manage roles or to the Users page in Space settings.
If you don’t see those in your experience, your instance hasn’t been enabled for roles yet.
Roles make managing user access to spaces consistent, predictable, and scalable. Each role has a different set of individual permissions associated with it, giving you confidence in what each user can do.
You can also assign roles broadly to different classes of users like All Confluence users or All Confluence admins, regardless of group membership.
Confluence’s roles
Confluence has four default roles, as well as the ability to define custom roles.
View the specific permissions included in each default role
管理Manages everything in the space. Best for: IT teams, Space owners | マネージャーManages people and content but not settings. Best for: Project leads, Team leads |
協力者Adds and edits content in the space. | ViewerViews and comments on content in the space. |
How the legacy permissions map to Confluence’s roles
The legacy space permissions table has a new look in the new world of Confluence roles. Here’s how it all fits together.
Legacy permissions |
| ロールの権限 |
|---|---|---|
All | “View content” | |
All | “Delete own content“ | |
Pages, whiteboards, databases, and Smart Links | “Create content“ | |
Pages, whiteboards, databases, and Smart Links | “Archive any content in the space“ | |
Pages, whiteboards, databases, and Smart Links | “Delete anyone’s content“ | |
Blogs | “Create blogs“ | |
Blogs | “Delete blogs“ | |
Comments | “Comment on content“ | |
Comments | “Delete anyone’s comments“ | |
Attachments | “Add attachments“ | |
Attachments | “Delete attachments“ | |
Restrictions | “Manage user access to content“ | |
Space | “Export space“ | |
Space | “Manage everything in space“ | |
New permissions Anyone who had the Admin permission before will still have these new permissions in the new experience. No one will automatically have these new permissions if they didn’t have the old Admin permission. | ||
NEW | - | “Manage user access to space“ |
NEW | - | “Allow and manage public links“ |
NEW | - | “Manage guest access to space“ |
NEW | - | “Allow anonymous access“ |
NEW | - | “Delete space” |
NEW | - | “Archive space” |
NEW | - | “Edit content” |
NEW | - | “Edit blogs” |
NEW | - | “Export individual content items” |
Specific permissions in each role
Permissions included with the Admin role
Permissions included with the Manager role
Permissions included with the Collaborator role
Permissions included with the Viewer role
この内容はお役に立ちましたか?