This page lists the scopes declared in the app manifest.yml
, explaining why each scope is required. Forge scopes and permissions are explained in detail in https://developer.atlassian.com/platform/forge/manifest-reference/scopes-product-confluence/#classic-scopes.
Scopes
...
On top of per-app scopes and permissions, there are additional permissions that CSUMCloud expects the Privileged User () to have, to allow the user to perform specific operations (For example, the privileged user must have permission to remove group members from a space if they wish to use the ‘Remove User’ operation).
Scopes
Scopes | Why required |
---|---|
| To allow App storage API (For Global Settings). Any setting stored are shown in System Admin Documentation |
|
View Space Details
- write:space:confluence
Update Space details (Space Permissions)
- delete:space:confluence
Delete Space details
- read:space.permission:confluence
View space permissions.
- write:space.permission:confluence
Update space permissions.
- read:user:confluence
View user details.
- read:group:confluence
View group details
- write:group:confluence
Update group details, create and delete groups
- read:space.property:confluence
View Space properties
- write:space.property:confluence
Update Space Properties
- read:content.permission:confluence
Content permission checks
- read:configuration:confluence
Get Confluence Settings, baseURL, etc
- write:configuration:confluence
Update Confluence Settings
- read:space-details:confluence
View Space Details, SpaceKeys
- read:content-details:confluence
View Content Details, Properties
- write:confluence-groups
Write access on confluence groups
Permissions
Permission
Why required
- unsafe-inline
To allow inline styles
- "*.atlassian.net"
| To allow view access for Confluence Global Settings. These include any global settings values, such as the System Info endpoint to allow Site base URL access (Used by the Privileged User to make site-internal |
Permissions
Permission | Why required |
---|---|
| To allow inline styles |
| To grant access to Atlassian site, allows access of user profile icons (Upcoming Feature) |
Privileged User Permissions
The list below is a collective total of permissions required. Please see the table below for detailed information on the reasoning (and usages) for each permission.
Permission to access the Confluence site ('Can use' global permission).
Permission to access the Confluence site ('Can use' global permission). Only content that the user has permission to view will be returned.
User must be a site admin.
'Admin' permission for the space.
This is a per-space requirement for each space you wish to use CSUMCloud with.
'View' permission for the space.
This is a per-space requirement for each space you wish to use CSUMCloud with.
Any further scope and permission information explanation can be found in the related Confluence Cloud REST API documentation.
Permission | Why required | REST API |
---|---|---|
Permission to access the Confluence site ('Can use' global permission). |
| |
User must be a site admin. |
| |
Permission to access the Confluence site ('Can use' global permission). |
| |
Permission to access the Confluence site ('Can use' global permission). |
| |
User must be a site admin. |
| |
User must be a site admin. |
| |
'View' permission for the space. |
| |
'View' permission for the space. |
| |
'Admin' permission for the space. |
| |
User must be a site admin. |
| |
User must be a site admin. |
| |
Permission to access the Confluence site ('Can use' global permission). Only content that the user has permission to view will be returned. |
|