> For the complete documentation index, see [llms.txt](https://helpcenter.xopero.com/xopero-one-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.xopero.com/xopero-one-en/backup-and-recovery/devops/bitbucket-dc/integration/required-permissions.md).

# Required permissions

## User permissions

In **Bitbucket Data Center**, user permissions can be managed in three ways, all of which are valid 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 allows the application to protect all repositories available on the **Bitbucket DC** instance.
2. **Project Permissions** — alternatively, you can assign **write** permissions at the project level to the user account connecting **Xopero ONE**. This approach restricts synchronization to repositories within specific projects only.
3. **Repository Permissions** — permissions can also be configured individually for each repository:

* [x] **Read** — sufficient to perform backups, but cannot be used to restore repositories.
* [x] **Write** — allows both backup and restore operations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpcenter.xopero.com/xopero-one-en/backup-and-recovery/devops/bitbucket-dc/integration/required-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.