> ## 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. # Bitbucket OAuth 2.0 connector profile – StackOne setup guide > Set up the OAuth 2.0 connector profile for Bitbucket in StackOne. One-time admin setup required before your users can link Bitbucket accounts via Hub. Administrator access to a Bitbucket workspace is required to create an OAuth consumer. The Account Read permission is required for the connection to work.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Creating an OAuth Consumer

To connect Bitbucket with StackOne, you'll need to create an OAuth consumer from your workspace settings.

Sign in to your Bitbucket account.

  • Select your avatar/profile from the top navigation
  • Choose your workspace from Recent workspaces or All workspaces
  • Click the Settings cog icon
  • Select Workspace settings from the dropdown

In the left sidebar, expand the Apps and features section, then click OAuth consumers.

Click the Add consumer button to create a new OAuth application.

  • Name: Enter a unique name (e.g., StackOne Integration)
  • Description: Optional description of the integration
  • Callback URL: Enter `https://api.stackone.com/connect/oauth2/bitbucket/callback`
  • URL: Optional link to your application
Enables actions: Add Default Reviewer, Approve Commit, Approve Pull Request, Create Branch Restrictions, Create Branches, Create Build, Create Comments, Create Commits, Create Deploy Key, Create Deploy Keys, Create Environment, Create Pipelines, Create Project, Create Pullrequests, Create Repository, Create Schedules, Create Src, Create Ssh Keys, Create Variables, Decline Pull Request, Delete Branch Restrictions, Delete Comments, Delete Default Reviewer, Delete Default Reviewers, Delete Deploy Key, Delete Deploy Keys, Delete Project, Delete Reports, Delete Repository, Delete Schedules, Delete Ssh Keys, Delete Variables, Get Authenticated User, 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 SSH Key, Get Schedules, Get Src, Get Steps, Get User, 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 Permissions, List Pipelines, List Projects, List Pull Request Commits, List Pullrequests, List Reports, List Repositories In Workspace, List Repository Groups, List Repository Permissions, List Schedules, List Src, List Ssh Keys, List Statuses, List Steps, List User Repository Permissions, List Variables, List Watchers, List Workspace Members, List Workspace Repository Permissions, 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 Deploy Keys, Update Environment, Update Pipelines Config, Update Project, Update Pullrequests, Update Reports, Update Schedules, Update Settings, Update Ssh Keys, Update Variables

Select the required OAuth permissions for your integration based on which Bitbucket resources you need to access. Permissions are configured on the OAuth consumer and cannot be changed per authorization request.

  • Account (Required): Read permission is required for the connection. Selecting Account Read automatically enables Account Email as a dependency. Write is optional (modify account properties).
  • Projects: Read (view projects and repositories), Admin (full admin access)
  • Repositories: Read, Write, Admin (view/edit permissions, deploy keys), Delete
  • Pull requests: Read (view pull requests), Write (create, merge, and decline pull requests)
  • Pipelines: Read (view pipelines and environments), Write (stop, rerun, trigger), Edit variables (create pipeline variables)
  • Select only the permissions required for your specific integration needs

Click Save to create the OAuth consumer. After saving, you will be redirected to the OAuth consumers list.

  • Click the chevron arrow (›) next to your consumer name to expand and reveal the credentials
  • The Key is your Client ID
  • The Secret is your Client Secret
  • Copy both values and store them securely for use later
## Creating the StackOne Connector Profile To create the Connector Profile in StackOne for Bitbucket: Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)
  • Click + Connector Profile
  • Search for and select Bitbucket
  • Select Type as OAuth 2.0
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
 Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Bitbucket.