Permissions & Scopes
If you're building on top of Sentry's API (i.e using Auth Tokens), you'll need certain scopes to access different API endpoints.
To set the scopes for an integration token, select the scopes from the dropdown. These can be edited later.
To set the scopes for an personal token, select the scopes from the dropdown when creating a personal token. These cannot be edited later.
If you're looking for information on membership roles please visit the membership documentation.
| GET | org:read |
| PUT/POST | org:write |
| DELETE | org:admin |
| CI Workflows | org:ci |
Use the org:ci scope for CI and deployment workflows, including uploading source maps, creating releases, and managing code mappings.
| GET | project:read |
| PUT/POST | project:write |
| DELETE | project:admin |
Note
The project:releases scope will give you access to both project and organization release endpoints. The available endpoints are listed in the Releases section of the API Documentation.
| GET | team:read |
| PUT/POST | team:write |
| DELETE | team:admin |
| GET | member:read |
| PUT/POST | member:write |
| DELETE | member:admin |
| GET | event:read |
| PUT | event:write |
| DELETE | event:admin |
Note
PUT/DELETE methods only apply to updating/deleting issues. Events in Sentry are immutable and can only be deleted by deleting the whole issue.
| GET/PUT/POST/DELETE | project:releases |
Note
Be aware that if you're using sentry-cli to manage your releases, you'll need a token which also has org:read scope.
Project Access
A personal token (user auth token) with the project:releases scope can create releases and upload artifact bundles for any project in the organization, even if Open Membership is disabled and the user isn't a member of the project's team. This lets tools like sentry-cli upload to multiple projects with a single token.
Changes to existing releases (updates, deletes, legacy release file uploads, and deploys) still require that the user has access to all projects associated with the release. If your organization has Open Membership disabled, members can only modify existing releases for projects belonging to teams they're a member of.