Required permissions

Permissions required to integrate Bitbucket Data Center with Xopero ONE to protect its resources.

To protect a Bitbucket Data Center (DC) environment with Xopero ONE, the account used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup.

---

Supported platform versions

Xopero ONE supports Bitbucket Data Center (DC) version 3.0.4 and higher, enabling comprehensive repository and metadata protection regardless of the underlying host operating system.

---

Account permissions

For Bitbucket DC integrations, an HTTP access token can be used in place of a password. Since these tokens inherit your user account's existing privileges, ensure you restrict the token's permissions to the access levels required for Xopero ONE operations before connecting.

In Bitbucket Data Center, account permissions can be managed in three distinct ways, all of which are fully supported for use with Xopero ONE:

1. Global permissions — the user account connecting Bitbucket DC with Xopero ONE must have at least administrator privileges. Using global permissions grants the application access to protect all repositories across the entire Bitbucket DC instance.

2. Project permissions — alternatively, you can assign write permissions at the project level to the connecting user account. This method restricts Xopero ONE synchronization and backup scope strictly to the repositories within those specific projects.

3. Repository permissions — permissions can also be configured individually for each specific repository, offering granular control via two operational tiers:

   1. Read (sufficient to perform data backups, but cannot be used to execute repository restorations).

   2. Write (full authorization to perform both backup and restoration operations).

---

Useful links and items

Users and groups | Bitbucket Data Center 10.3 | Atlassian Documentationconfluence.atlassian.com