> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/version-control-repository/bitbucket/configuring-bitbucket-token-authentication-and-email-support.md).

# Configuring Bitbucket Token Authentication and Email Support

### Introduction

Bitbucket is deprecating App Password authentication effective **June 9, 2026**. To ensure uninterrupted connectivity and support for Bitbucket API operations, AutoRABIT supports Token-based authentication and provides an Email Address field for Bitbucket credentials.

This guide explains how to configure and update Bitbucket credentials in AutoRABIT.

***

### Prerequisites

Before proceeding, ensure that:

* You have access to your Bitbucket account.
* A Bitbucket App Token has been generated.
* You know the email address associated with your Bitbucket account.

***

### When Is an Email Address Required?

An email address is required for Bitbucket API-based operations such as:

* Pull Request Creation
* Other Bitbucket REST API operations

The email address is not required for Git operations such as:

* Clone
* Fetch
* Push

***

### Configuring a New Bitbucket Credential

#### New UI

1. Navigate to **Settings → Credentials**.
2. Click **Create Credential**.
3. Select **Bitbucket** as the repository type.
4. Enter the following information:
   * Username
   * Token
   * Email Address (Optional)
5. Click **Save**.

<figure><img src="/files/iZEdljJiBfMm10sVYX0h" alt=""><figcaption></figcaption></figure>

### Updating an Existing Bitbucket Credential

1. Navigate to **Settings → Credentials**.
2. Locate the Bitbucket credential.
3. Click **Edit**.
4. Enter or update the **Email Address** field.
5. Save the changes.

<figure><img src="/files/EECDFhNeWI4dUl6eAPme" alt="" width="375"><figcaption></figcaption></figure>

***

### Repository Registration

When registering a Bitbucket repository:

1. Select the Bitbucket credential.
2. Verify that the credential contains:
   * Username
   * Token
   * Email Address (recommended)
3. Complete repository registration.

***

### Updating Version Control Mappings (New UI)

1. Navigate to **My Profile → Version Control Mappings**.
2. Select the Bitbucket credential.
3. Verify the Email Address is configured.
4. Save the mapping.

<figure><img src="/files/V1Iqnv25kFXAKXluhSS9" alt=""><figcaption></figcaption></figure>

***

### Best Practices

* Migrate from App Passwords to Tokens before June 9, 2026.
* Configure an Email Address for all Bitbucket credentials used for Pull Request workflows.
* Periodically review and update repository credentials.

***

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/version-control-repository/bitbucket/configuring-bitbucket-token-authentication-and-email-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.