OAuth 2.0 scopes for incoming links

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When configuring incoming links with external applications, you need to select scopes, which are permissions the application can have on your instance.

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.

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.

ScopeDescription

READ

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.

WRITE

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.

ADMIN

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.

SYSTEM_ADMIN

Administer Jira system

Perform all administrative functions on the entire Jira instance, including functions such as backups, imports, and infrastructure settings.

Last modified on Aug 30, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.