Get started with Bitbucket Cloud
New to Bitbucket Cloud? Check out our get started guides for new users.
Repository Access Tokens are single-purpose, repository-based access tokens that can be created with limited scopes (or permissions). The following types of scope are available for Repository Access Tokens:
To determine which scopes (permissions) the Repository Access Token will need, look up the APIs you need in the Bitbucket Cloud Developer Documentation.
Repository permissions provide access to view or modify Bitbucket Cloud repositories. Bitbucket Cloud allows the following repository permission levels:
Read
Write
Admin
Delete
Equivalent to the repository API scope.
Provides access to view repositories, including the source code. This does not include pull requests.
Equivalent to the repository:write API scope.
Provides access to modify repositories, including the source code. This does not include pull requests.
Equivalent to the repository:admin API scope.
Provides access to administrator access to repositories. This permission (scope) allows the user to:
View and manipulate committer mappings.
List and edit deploy keys.
Ability to delete the repositories.
View and edit repositories permissions.
View and edit branch permissions.
List and edit default reviewers.
List and edit repository links (such as Jira, Bamboo, and custom links).
List and edit the repository webhooks.
Initiate a repository ownership transfer.
Equivalent to the repository:delete API scope.
Provides access to delete repositories.
Pull request permissions provide access to view or modify Bitbucket Cloud pull requests. Bitbucket Cloud allows the following pull request permission levels:
Read
Write
Equivalent to the pullrequest API scope.
Provides access to view and list pull requests. This permission (scope) also allows the user to create and resolve tasks.
Equivalent to the pullrequest:write API scope.
Provides access to create, comment, approve, decline, and merge pull requests.
The Webhooks permission provides read and write access to existing webhooks, allowing for the creation of webhooks when combined with other permissions. For details, see: Bitbucket Cloud REST APIs — Webhooks.
Equivalent to the webhook API scope.
Required for webhook operations. Additional API scopes may be required. For details, see: Bitbucket Cloud REST APIs — Webhooks.
Pipelines permissions provide access to view or control Bitbucket Pipelines. Bitbucket Cloud allows the following pipeline permission levels:
Read
Write
Edit variables
Equivalent to the pipeline API scope.
Provides access to view the pipelines, steps, deployment environments, and variables.
Equivalent to the pipeline:write API scope.
Provides access to stop, rerun, resume, and manually trigger pipelines.
Equivalent to the pipeline:variable API scope.
Provides access to create pipelines environmental variables in repositories and deployments.
Runners permissions provide access to view or modify Bitbucket Pipelines Runners for a repository or repositories. Bitbucket Cloud allows the following pipeline runner permission levels:
Read
Write
Equivalent to the runner API scope.
Provides access to view the pipelines runners for a repository or repositories.
Equivalent to the runner:write API scope.
Provides access to create, edit, disable, and delete pipelines runners for a repository or repositories.
Was this helpful?