Confluence roles and space permissions
Confluence spaces support different permission capabilities that control what users can do within a space.
| Permission capability | Description |
|---|---|
| View | Allows users to view pages, blog posts, and attachments in the space. |
| Add content | Allows users to create pages, blog posts, and attachments. |
| Edit content | Allows users to edit existing pages and blog posts. |
| Delete content | Allows users to remove pages, comments, and attachments. |
| Add comments | Allows users to comment on pages and blog posts. |
| Restrict pages | Allows users to set page-level restrictions. |
| Space administration | Allows users to manage space permissions and settings. |
These permissions can be granted to individual users or user groups.
How permissions are managed in SHIP-HATS
| Assignment type | Assigned via |
|---|---|
| User groups | Console and Confluence |
| Individual users | Confluence |
Permissions configured through Console are reflected in the associated Confluence space, and vice versa.
SHIP-HATS to Confluence role mapping
When a Confluence space is created through Console, certain roles are mapped automatically.
| SHIP-HATS role | Confluence role | Description |
|---|---|---|
| Project Admin (PA) | Space Administrator | Automatically assigned as space administrator when the Confluence space is created. Can manage space permissions and add users or groups. Multiple space administrators are allowed. |
| Users | Space User | Can be granted permissions at space level, either individually or through group membership. |
Important
- Being a SHIP-HATS Project Admin does not automatically grant access to a space unless:
- The user has a valid Atlassian (Jira & Confluence) licence, and
- The user has been granted space permissions.
- Additional space administrators can be added manually.
- Removing space administrator permissions revokes administrative control but does not remove the Atlassian licence.
How permissions behave
- Confluence space permissions are additive.
- If a user receives permissions:
- Through group membership, and/or
- Through individual assignment
- All permissions combine to determine the user’s effective access.
- Page-level restrictions may further limit visibility even when space permissions are granted.
For detailed permission definitions, refer to Atlassian documentation:
Open Data Access (GovTech subscriptions only)
GovTech-owned SHIP-HATS subscriptions may be subject to Open Data Access (ODA).
Open Data Access grants predefined Confluence space permissions through centrally managed Atlassian user groups. These permissions are applied at the space level and follow the same additive behaviour described above.
For details, see Open Data Access (GovTech subscriptions only).
