
Govern Bitbucket repo access the same way you govern the rest
Connect Bitbucket OAuth, import repositories, and Sync permission levels when grants are approved — so Atlassian repo access is requested and reviewable.
How it works
From Bitbucket OAuth to Sync’d access
Connect once, import the repos you govern, then Sync permissions when grants are approved.
01
Connect Bitbucket
Authorize Approv with Bitbucket OAuth for the workspace you manage.
02
Import repositories
Select Bitbucket repositories to govern as Approv resources.
03
Request → approve → Sync
Members request a level. On approve, Approv Syncs Bitbucket permissions and records who granted what.
Connect
Connect Bitbucket OAuth once
Authorize your workspace. Approv stores tokens encrypted and can list the repositories you choose to govern — so Atlassian repo access is requested and reviewable.
- One OAuth connect per org workspace
- Import only the repos you want under Approv governance
- Tokens stay encrypted at the organization level

Resources
What you can govern in Bitbucket
Import these resources into Approv, then approve access with mapped Bitbucket permissions.
01
Repositories
Import Bitbucket repos and govern read, write, or admin access.
02
Workspace-aware
Connect once per org and import the repos your team actually needs.
03
Revocable grants
Expired or revoked grants Sync removal in Bitbucket.

Sync
Approved grants become Bitbucket permissions
On approve, Approv Syncs the mapped repository permission. On revoke or expire, that access is removed — so Bitbucket access stays reviewable and time-bound.
- Read, write, and admin mapped to native Bitbucket roles
- Time-bound access that Syncs removal when it ends
- Audit trail of who approved what, and when
Mapping
Permission mapping
Approv permission levels map to native Bitbucket roles when Sync runs.
| In Approv | In Bitbucket |
|---|---|
| Read | read |
| Write | write |
| Admin | admin |
Frequently Asked Questions
Connect, import, and Sync for Bitbucket repositories.