Rate limits are enforced for security and stability— excessive requests may block access or disrupt the application’s operation. For detailed information, refer to the .
This article provides instructions for adding a Bitbucket organization to GitProtect.
Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the Connect button under Bitbucket.
A pop-up with Bitbucket login page will appear. Log in using your admin credentials and grant GitProtect access to the specified resources (when prompted).
Your Bitbucket organization has now been successfully added to GitProtect. Click Custom policy to adjust your backup policy settings, or click Run backup to execute the backup immediately using the current policy configuration.
Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the advanced mode link under Bitbucket and Bitbucket DC tiles.
Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the advanced mode link under Bitbucket and Bitbucket DC tiles.
When adding an organization, you may be prompted to grant additional permissions to the GitProtect application—make sure your browser allows GitProtect to open pop-up windows.
Depending on your browser, you can either adjust the settings to allow pop-ups or permit the authorization window to open once.
Set your authentication method.
In Authentication, select Bitbucket.
For Connect using, choose OAuth App.
In the Settings section, choose whether to enable read-only mode and whether GitProtect should automatically add new repositories to your backup.
Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.
Click Proceed to complete adding your Bitbucket organization and grant GitProtect access to the specified resources (when prompted).
Set your authentication method.
In Authentication, select Bitbucket.
For Connect using, choose Username and App password.
Enter your Bitbucket email address.
Add or select App Password that contains your API token from the Password Manager.
Choose whether GitProtect should automatically add new repositories to your backup.
Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.
Click Proceed to complete adding your Bitbucket organization and grant GitProtect access to the specified resources.













Permissions required to integrate Bitbucket with GitProtect to protect its resources.
To protect a Bitbucket environment with GitProtect, the account or token used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup. The specific permission scopes vary depending on the chosen authorization method.
When integrating Bitbucket using the OAuth authentication method, GitProtect requires the following permissions to securely access and protect your repository data:
Issues
Read and modify repositories' issues.
Pipelines
Access repositories' build pipelines and configure their variables.
Project settings
Read and modify workspace's project settings.
Read and transfer repositories within workspace's projects.
Repositories & pull requests
Administer repositories.
Delete repositories.
Read and modify repositories and their pull requests.
Manage runners
Access and edit workspaces and repositories' runners.
Snippets
Read and modify code snippets.
Team membership
Read and modify team membership details.
Workspaces
Access your workspaces for authentication.
Access and edit your workspaces and repositories' test.
Webhooks
Read and modify repositories' webhooks.
Wikis
Read and modify repositories' wikis.
Every API token created for Bitbucket integration with GitProtect requires specific permission scopes to restrict data access and define the exact operations the token can execute.
To ensure successful backup and recovery tasks, API token must be provisioned with the below required permissions.
read:webhook:bitbucket (hooks)
read:user:bitbucket (required to link the organization)
read:repository:bitbucket (repositories, downloads, synchronization)
read:pullrequest:bitbucket (pull requests)
read:pipeline:bitbucket (schedules)
read:pullrequest:bitbucket (pull requests)
read:webhook:bitbucket (hooks)
read:issue:bitbucket (issues)
read:issue:bitbucket (issues)
read:wiki:bitbucket (wiki)
admin:repository:bitbucket (branch restriction rules, deployment keys, branching models)
read:wiki:bitbucket (wiki)
write:wiki:bitbucket (wiki)
write:webhook:bitbucket (hooks)
write:ssh-key:bitbucket (deployment keys)
write:repository:bitbucket (repositories, downloads)
write:pullrequest:bitbucket (pull requests)
write:pipeline:bitbucket (schedules)
write:issue:bitbucket (issues)
admin:pipeline:bitbucket (known hosts, variables)
admin:repository:bitbucket (repositories, schedules, deployment keys, advanced details, branching models, branch restrictions)
admin:project:bitbucket (project — in some cases, creation is required to restore the repository)
read:repository:bitbucket (required for synchronization, repositories)
read:user:bitbucket (required to link the organization, repositories)


