ConductorOne Docs

Bitbucket integration

ConductorOne provides identity governance for Bitbucket. Integrate your Bitbucket instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.


Bitbucket Cloud is a Git-based code and CI/CD tool optimized for teams using Jira.


βœ… General availability. The Bitbucket integration is available to all ConductorOne users.


  • Sync user identities from Bitbucket to ConductorOne
  • Supported resources:
    • Workspaces
    • Groups
    • Projects
    • Repositories

Set up the Bitbucket integration

A user with the Super Administrator role in ConductorOne must perform this task.

  1. In ConductorOne, open Administer and click Integrations > Bitbucket.

  2. If this is your first Bitbucket integration, the integration form opens automatically. Otherwise, click Add connector.

  3. Choose whether to add the new Bitbucket connector to an existing application (and select the app of your choice) or to create a new application.

    Do you SSO into Bitbucket using your identity provider (IdP)? If so, make sure to add the connector to the Bitbucket app that was created automatically when you integrated your IdP with ConductorOne, rather than creating a new app.

  1. Set the integration owner for this connector. You can manage the integration yourself, or choose someone else from the list of ConductorOne users. Setting multiple integration owners is allowed.

    A Bitbucket integration owner must have the following permissions:

    • Integration Administrator or Super Administrator role in ConductorOne
    • Permission to create an OAuth consumer for the Bitbucket Cloud workspace you’re integrating
  1. Click Create and add details.

Next steps

  • If you are the integration owner, proceed to Integrate your Bitbucket instance for instructions on integrating Bitbucket with ConductorOne.

  • If someone else is the integration owner, ConductorOne will notify them by email that their help is needed to complete the integration.

Integrate your Bitbucket instance

A user with the Integration Administrator or Super Administrator role in ConductorOne and the permission to create an OAuth consumer in Bitbucket must perform this task.

Step 1: Create an OAuth consumer

  1. In the Bitbucket workspace you want to integrate with ConductorOne, click Settings (gear icon) in the top right corner of the screen and then click Workspace settings.

  2. In the menu on the left side of the page, click OAuth consumers.

  3. Click Add consumer.

  4. Give your new consumer a name, such as “ConductorOne integration”.

  5. In the Callback URL field, enter https://localhost. Leave the other URL fields blank.

  6. Check the box to select This is a private consumer.

  7. In the Permissions section of the page, select the following permissions:

    • Account: Read
    • Workspace membership: Read
    • Projects: Read, Admin
    • Repositories: Admin
  8. Click Save.

  9. Your new consumer is now shown in the list of OAuth consumers. Click on your new consumer’s name to display the consumer key and secret.

  10. Carefully save the consumer’s key and secret. We’ll use these in Step 2.

Step 2: Add your Bitbucket credentials to ConductorOne

  1. In ConductorOne, open Administer and click Integrations > Bitbucket.

  2. In the list of connectors, locate and click on the name of the connector with the Not connected label.

  3. Find the Settings area of the page and click Edit.

  4. Enter the consumer key and consumer secret created in Step 1 into the Consumer Key and Consumer Secret fields.

  5. Click Save.

  6. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Bitbucket instance is now integrated with ConductorOne.

Configure the Bitbucket integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Bitbucket and ConductorOne.

See the ConductorOne Bitbucket integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.