Managing HTTP access tokens
Project and repository administrators can create HTTP access tokens for their projects and repositories. Users can create personal HTTP access tokens and use them in place of passwords for Git over HTTPS, or to authenticate when using the Bitbucket Data Center REST API. As an administrator, you can edit and revoke tokens, and set global token settings.
On this page:
Related pages:
Editing and deleting tokens
As an administrator, you can’t create tokens for users. However, once a user has created a token, you can edit or delete it.
To edit or delete a personal HTTP token:
Go to
> Users.Search for the user and click on them.
Open the HTTP access tokens tab.
Select Edit or Delete.
To edit or delete a project or repository's HTTP token:
- From either the Project or Repository settings, select HTTP access tokens.
- Select Edit or Delete.
Selecting Edit will allow you to change a token’s name or its permissions. If it has an expiry date, however, you will not be able to modify it. Once a token’s expiry date has been set, it can’t be changed.
Require token expiry
By default, when a user is creating a personal access token, they can choose whether they want it to expire. As a system administrator, for added security you can make setting a token expiry a requirement.
To require token expiry:
Go to
> Keys and tokens (under System).Select Yes for Automatic expiry.
Enter the HTTP access token expiry (in days).
Select Save.