---
title: "Access Tokens"
canonical: "https://support.appfire.com/space/SCLI/73368178/Access%20Tokens"
format: markdown
---
# Description

Starting with Bitbucket 5.5 (server and data center), you can use personal access tokens many CLI actions and REST API requests instead of using basic authentication with user and password. See [Bitbucket Personal Access Tokens](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html) for more details. An access token can be specified on the ***token*** parameter on CLI actions related to repositories.

The CLI also supports actions for managing access tokens: add, remove, and getAccessTokenList.

From the UI, go to ***Manage account*** and ***Personal access tokens.***

For Bitbucket Cloud, a similar thing is available called **App passwords** (see below for more information)**. **From a browser: Login → View profile → Settings → App passwords.

For more information, see [Authentication options](https://appfire.atlassian.net/wiki/spaces/ACLI/pages/60563795).

# Permission Table

See the Atlassian [documentation](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html) for the current information. Here is a snapshot of that with some additional information including the valid values for the ***permission*** parameter on ***addAccessToken.***

|  | **Project read - **<span style="color: #091e42">**PROJECT_READ**</span> | **Project write - **<span style="color: #091e42">**PROJECT_WRITE**</span> | **Project admin - **<span style="color: #091e42">**PROJECT_ADMIN**</span> |
| --- | --- | --- | --- |
| **Repository read**<br><span style="color: #091e42">**REPO_READ**</span> | :check_mark: Pull and clone repositories | :cross_mark: | :cross_mark: |
| <span style="color: #000000">**Repository write**</span><br><span style="color: #091e42">**REPO_WRITE**</span> | :check_mark: Perform pull request actions<br>:check_mark: Push, pull, and clone repositories | :check_mark: Perform pull request actions<br>:check_mark: Push, pull, and clone repositories | :cross_mark: |
| <span style="color: #000000">**Repository admin**</span><br><span style="color: #091e42">**REPO_ADMIN**</span> | :check_mark: Perform pull request actions<br>:check_mark: Update repository settings and permissions<br>:check_mark: Push, pull, and clone repositories | :check_mark: Perform pull request actions<br>:check_mark: Update repository settings and permissions<br>:check_mark: Push, pull, and clone repositories | :check_mark: Perform pull request actions<br>:check_mark: Update repository settings and permissions<br>:check_mark: Update project settings and permissions<br>:check_mark: Push, pull, clone, and fork repositories<br>:check_mark: Create repositories |

# Examples

```
--action addAccessToken  --name "project-admin"  --permission "PROJECT_ADMIN, REPO_ADMIN"
```

# Other Information

- [BSERV-10482](https://jira.atlassian.com/browse/BSERV-10482) - Create admin personal tokens for admin endpoints in Bitbucket Server REST API

# Cloud App Passwords

> <span style="color: #172b4d">App passwords are substitute passwords for a user account which you can use for scripts and integrating tools to avoid putting your real password into configuration files.</span>

<span style="color: #172b4d">For more information, see: </span>[<span style="color: #172b4d">App Passwords</span>](https://confluence.atlassian.com/bitbucket/app-passwords-828781300.html)<span style="color: #172b4d">.</span>

> ❌ **Use account name with app passwords**
> ❌ 
> ❌ Make sure you use your Bitbucket account name and NOT your email address when using App passwords!


- Login → View profile → Settings → App passwords

![image](media://af87d36b-bd8e-4398-b42a-f9971c02fc89)