Last updated Sep 18, 2025

Ending Connect support

You can no longer publish Connect apps on the Atlassian Marketplace. All new extensibility features will be delivered only on Forge.

Refer to this blog post for our timeline to end Connect support.

Have an existing Connect app? You can incrementally migrate it to Forge.

Scopes for Connect apps

Scopes enable an app to request a level of access to an Atlassian product.

The scopes may provide the potential to access beta or non-public APIs that are later changed or removed from the Atlassian product. The inclusion of the API endpoint in a scope doesn't imply that the product makes this endpoint public. Read the Jira Cloud platform REST API documentation for details.
Some scopes automatically imply that the app is granted other scopes.

If you are building an Atlassian Connect app for Jira, use the following scopes:

Scope name	Description	Implied scopes
`NONE`	Access app-defined data. This scope does not need to be declared in the descriptor.
`READ`	View, browse, and read information from Jira.	`NONE`
`WRITE`	Create or edit content in Jira, but not delete content.	`READ`, `NONE`
`DELETE`	Delete content in Jira.	`WRITE`, `READ`, `NONE`
`PROJECT_ADMIN`	Administer a project in Jira.	`DELETE`, `WRITE`, `READ`, `NONE`
`ADMIN`	Administer the Jira site.	`PROJECT_ADMIN`, `DELETE`, `WRITE`, `READ`, `NONE`
`ACT_AS_USER`	Access content using the permissions of the user running the app.
`ACCESS_EMAIL_ADDRESSES`	Get the email addresses of users.

Scope names can be provided in all lowercase or all upper case, for example, read or READ.

Scopes are declared as a top level attribute of atlassian-connect.json app descriptor as in this example:

1
2
{
    "baseUrl": "http://my-app.com",
    "key": "atlassian-connect-app",
    "scopes": [
        "read", "write"
    ],
    "modules": {}
}