OAuth 2.0 scopes for incoming links
When creating incoming links from external application, you need to select scopes, which are permissions the application can have on your instance.
What the application can do with scopes
As an admin, you can select which scopes the application can request from the authorizing user, but the actual permissions will always be capped at what this user can do. For example, even if you select the ADMIN permissions, the application won’t be able to use them if the authorizing user only has WRITE permissions.
Scopes
Here are the scopes you can select when configuring the link. The same scopes will be displayed to users when they authorize the integration. They can later be accessed in their user profile in Authorized applications, where they can also revoke the granted access.
Scope | Description |
|---|---|
READ | View content View content your account can view, including spaces, pages, blog posts, custom content, attachments, comments, and templates. Also view your user profile. |
WRITE | Create, update, and delete content Create, update, and delete content your account can change, including spaces, pages, blog posts, custom content, attachments, comments, and templates. Also change your user profile. |
ADMIN | Administer Confluence Perform most administrative functions on the entire Confluence instance, excluding functions such as backups, imports, and infrastructure settings which are limited to system administrators. |
SYSTEM_ADMIN | Administer Confluence system Perform all administrative functions on the entire Confluence instance, including functions such as backups, imports, and infrastructure settings. |