OAuth 2.0 scopes for incoming links
When configuring incoming links with external applications, 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 |
|---|---|
| View projects and issues View projects and issues your account can view, including any related items, such as dashboards, filters, attachments, or comments. Also view your user profile. |
| Create, update, and delete projects and issues Create, update, and delete projects and issues your account can change, including any related items, such as dashboards, filters, attachments, or comments. Also change your user profile. |
| Administer Jira Perform most administrative functions on the entire Jira instance, excluding functions such as backups, imports, and infrastructure settings which are limited to system administrators. |
| Administer Jira system Perform all administrative functions on the entire Jira instance, including functions such as backups, imports, and infrastructure settings. |