> ## 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 (Atlassian Identity Platform) connector profile – StackOne setup guide > Set up the OAuth 2.0 (Atlassian Identity Platform) connector profile for Bitbucket in StackOne. One-time admin setup required before your users can link Bitbucket accounts via Hub.
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

Configure Permissions

Select the required permissions on the OAuth consumer. Migrated consumers grant these as granular scopes rather than the legacy checkbox labels.

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 Unified Credentials, Get Unified Organization, Get Unified Role, Get Unified User, 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 Unified Organizations, List Unified Resource Types, List Unified Roles, List Unified Users, 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

If the consumer settings page still shows the legacy labels (e.g. "Account", "Repositories") instead of the scopes below, your consumer has not actually been migrated yet — use the "OAuth 2.0 (Legacy)" option instead.

  • Account (Required): `read:account:bitbucket-legacy` is required for the connection. Write is optional (modify account properties).
  • Projects: read, 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), admin (create pipeline variables)
  • Select only the permissions required for your specific integration needs
## 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 (Atlassian Identity Platform)
  • 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.