Permissions and Scopes
Audit 360 for Confluence requests read-only Atlassian API scopes to support audit workflows. No write scopes are requested.
Scopes requested
| Scope | Purpose |
|---|---|
read:confluence-space.summary | List spaces and retrieve space metadata for Spaces Audit. |
read:confluence-props | Read space and page properties for configuration signals. |
read:confluence-content.all | Read page metadata (title, status, last modified) for content scanning. |
read:confluence-user | Resolve user profiles for permission and ownership signals. |
read:confluence-groups | Resolve group membership for Permission Audit. |
What is not requested
- No write scopes.
- No content-creation or deletion scopes.
- No admin-mutation scopes.
Forge platform isolation
Audit 360 for Confluence runs on Atlassian Forge. Each installation is isolated — data is stored in Forge SQL associated with your specific Confluence site installation. No data is shared between installations or sites.