Documentation

Scopes

Scopes allow an add-on to request a particular level of access to an Atlassian product.

For example:

  • Within a particular product instance an administrator may further limit the actions that an add-on may perform. This is valuable because it allows administrators to safely install add-ons that they otherwise would not.
  • The scopes may allow the potential to access beta or non-public APIs that are later changed in or removed from the Atlassian product. The inclusion of the API endpoint in a scope does not imply that the product makes this endpoint public: read the product's API documentation for API details.

Note: Some scopes automatically imply that the add-on will be granted other scopes; there are defined below.

The following scopes are available for use by Atlassian Connect add-ons:

JIRA

  • NONE – can access add-on defined data - this scope does not need to be declared in the descriptor.
  • READ – can view, browse, read information from JIRA
  • WRITE – can create or edit content in JIRA, but not delete them (implies: READ)
  • DELETE – can delete entities from JIRA (implies: READ, WRITE)
  • PROJECT_ADMIN – can administer a project in JIRA (implies: READ, WRITE, DELETE)
  • ADMIN – can administer the entire JIRA instance (implies: READ, WRITE, DELETE, PROJECT_ADMIN)
  • ACT_AS_USER – can enact services on a user's behalf.

See the following pages for details on which remote endpoints are available in JIRA:

Confluence

  • NONE – can access add-on defined data - this scope does not need to be declared in the descriptor.
  • READ – can view, browse, read information from Confluence
  • WRITE – can create or edit content in Confluence, but not delete them (implies: READ)
  • DELETE – can delete entities from Confluence (implies: READ, WRITE)
  • SPACE_ADMIN – can administer a space in Confluence (implies: READ, WRITE, DELETE)
  • ADMIN – can administer the entire Confluence instance (implies: READ, WRITE, DELETE, SPACE_ADMIN)
  • ACT_AS_USER – can enact services on a user's behalf.

See the following pages for details on which remote endpoints are available in Confluence:

Example

Scopes are declared as a top level attribute of the atlassian-connect.json descriptor:

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