> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Bitbucket with Workspace Access Token – StackOne Hub

> Link a Bitbucket account in the StackOne Hub using Workspace Access Token. End-user guide to authorize the integration and start using Bitbucket actions.

Select Actions to adjust the guideSome actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Select all
Clear

ActionScope(s)

Loading actions...No actions match your search.

Dynamic Guide URL

Copy URL

Scopes Selected

<pre role="textbox" aria-readonly="true" tabIndex="0" />

Separator

Copy scopes

## Creating a workspace access token

Workspace access tokens are a Bitbucket Cloud Premium feature. A workspace access token reaches only the workspace it was created in, including every project and repository in it.

**1. Open the access tokens page**

Sign in to [Bitbucket](https://bitbucket.org/account/signin/) as an administrator of the workspace, then open the workspace.

<ul>
  <li>Select the **Settings** cog on the top navigation bar.</li>
  <li>Select **Workspace settings**.</li>
  <li>In the left sidebar, under **Security**, select **Access tokens**.</li>
  <li>Select **Create access token**.</li>
</ul>

**2. Create the token**

Enables actions: Add Default Reviewer, Approve Commit, Approve Pull Request, Create Branch Restrictions, Create Branches, Create Build, Create Comments, Create Commits, Create Environment, Create Pipelines, Create Project, Create Pullrequests, Create Repository, Create Schedules, Create Src, Create Variables, Decline Pull Request, Delete Branch Restrictions, Delete Comments, Delete Default Reviewer, Delete Default Reviewers, Delete Deploy Key, Delete Project, Delete Reports, Delete Repository, Delete Schedules, Delete Variables, Get Branch Restrictions, Get Branches, Get Branching Model, Get Branching Model Settings, Get Build, Get Comments, Get Commit, Get Default Reviewer, Get Default Reviewers, Get Deploy Key, Get Deploy Keys, Get Deployment, Get Diff, Get Diffstat, Get Environment, Get Log, Get Logs, Get Patch, Get Pipelines, Get Pipelines Config, Get Project, Get Project Branching Model Settings, Get Pullrequests, Get Reports, Get Repository, Get Schedules, Get Src, Get Steps, Get Unified Organization, Get Variables, Get Workspace, List Branch Restrictions, List Branches, List Branching Model, List Comments, List Commits, List Default Reviewers, List Deploy Keys, List Deployments, List Downloads, List Environments, List Forks, List Pipelines, List Projects, List Pull Request Commits, List Pullrequests, List Reports, List Repositories In Workspace, List Schedules, List Src, List Statuses, List Steps, List Unified Organizations, List Variables, List Watchers, List Workspaces, Merge Pull Request, Remove Request Changes, Request Changes, Resolve Pull Request Comment, Stop Pipeline, Unapprove Commit, Unapprove Pull Request, Unresolve Pull Request Comment, Update Branch Restrictions, Update Build, Update Build Number, Update Comments, Update Default Reviewer, Update Environment, Update Pipelines Config, Update Project, Update Pullrequests, Update Reports, Update Schedules, Update Settings, Update Variables

Give the token a name and an expiry, then select every scope listed. To receive webhook events, also select the `webhook` permission.

<ul>
  <li>**Name**: `StackOne Integration`</li>
  <li>**Expiry**: The date the token should stop working, or **No expiry** if your workspace admin allows it</li>
  <li>Select **Create**.</li>
</ul>

<ul>
  <li>
    repository
  </li>

  <li>
    repository:write
  </li>

  <li>
    repository:admin
  </li>

  <li>
    repository:delete
  </li>

  <li>
    pullrequest
  </li>

  <li>
    pullrequest:write
  </li>

  <li>
    pipeline
  </li>

  <li>
    pipeline:write
  </li>

  <li>
    pipeline:variable
  </li>

  <li>
    project
  </li>

  <li>
    project:admin
  </li>

  <li>
    account
  </li>
</ul>

**3. Copy the token**

In the **Access token created** dialog, the token is shown only once and can't be retrieved later.

<ul>
  <li>Copy the **Access Token** across.</li>
</ul>

**4. Find the Webhook Workspace**

Only needed to receive webhook events. Your **Webhook Workspace** is the workspace slug in the address bar when you open the workspace in Bitbucket.

<ul>
  <li>Format: `https://bitbucket.org/{workspace}/`</li>
  <li>Example: if your URL is `https://bitbucket.org/acme-dev/`, your **Webhook Workspace** is `acme-dev`</li>
</ul>

## Link the Account

**1. Connect**

<ul>
  <li>Click **Connect**.</li>
  <li>If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.</li>
  <li>Once authorization is successful, you will see a confirmation popup.</li>
</ul>

**2. Use Actions**

Connect an AI platform to the linked account's actions. See [AI Platforms](https://docs.stackone.com/ai-platforms/overview.md).

Other ways to call actions are listed in [Protocols & SDKs](https://docs.stackone.com/connect/protocols-and-sdks.md).

## Next Steps

> [card] [Webhooks setup](https://docs.stackone.com/connectors/bitbucket/guides/webhook-setup.md)
>
> Configure receiving Events for Bitbucket into StackOne.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.