# Setting up Bitbucket in Avo Assure

This section explains how to set up Bitbucket in Avo Assure. You will connect Avo Assure to your Bitbucket account by providing the necessary credentials, repository URL, and API token."

To configure Bitbucket in Avo Assure, perform the following steps:

1. On the **Home** page, under **Projects**, select the required **Project**.&#x20;
2. Select **Manage Integration** link from **Settings** card.

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

3. Select the **Versioning** page, and select **Bitbucket**.
4. Enter the required configuration details:

* **Connection Name**: Enter a name for the Bitbucket connection.
* **Access Token**: Enter the token used to authenticate with your Bitbucket account.
  * **Personal access token (PAT)**: If you use a personal access token, then select the PAT checkbox and enter the token.

{% hint style="info" %}
**Note**: To know more about access tokens generation in Bitbucket, [click here](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/bitbucket-api-token-generation.md).
{% endhint %}

* **Repository URL**: Enter the URL of the Bitbucket repository.

{% hint style="info" %}
**Note:** To know more about how to get the Repository URL from Bitbucket, [click here](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/bitbucket-api-token-generation.md#getting-repository-url-in-bitbucket).
{% endhint %}

* **Username**: Enter Bitbucket Username associated with the account. &#x20;

{% hint style="info" %}
**Note**: To know more about how to get the Username from Bitbucket, [click here](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/bitbucket-api-token-generation.md#getting-username-in-bitbucket).
{% endhint %}

5. Select **Create** button to finalize the Bitbucket setup.

{% hint style="info" %}
**Note**: To reset the Bitbucket configuration, select the **Reset** button.
{% endhint %}

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

## Roles and permissions in Bitbucket

Bitbucket controls user access through roles and permissions configured at the repository and branch level.

You can manage access to Bitbucket repositories using the following permissions:

1. **Access Permissions**:

   All users can push to and pull from a Bitbucket repository. The actions they can perform depend on the permissions assigned to the repository and its branches in Bitbucket.
2. **Branch Policies**:

   Avo Assure does not restrict pushes to the master branch. Branch restrictions and policies are configured and enforced by the Bitbucket repository administrator.

The following Avo Assure roles can push test artifacts to Bitbucket and pull test artifacts from Bitbucket into Avo Assure.

<figure><img src="/files/0pQT7yhMuSRmbIBFVgIT" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Quality Engineer(QE) cannot push the test artifacts to Master Branch.
{% endhint %}

{% hint style="info" %}
To learn more about how Avo Assure Client improves Bitbucket push performance using Source Control Management (SCM) configuration parameters, [click here](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/setting-up-bitbucket-in-avo-assure/pushing-data-to-bitbucket-repository/improving-bitbucket-push-performance.md).

* This section explains how each parameter affects push speed and stability.
* It also guides you on adjusting the settings based on system capacity and project size.
  {% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/bitbucket/setting-up-bitbucket-in-avo-assure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
