> 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/confluence/integration/required-permissions.md).

# Required permissions

**Protecting Confluence in Xopero ONE requires a set of Atlassian permissions that allow secure authorization and read access to Confluence content, while also enabling the backup application to enumerate and retrieve site resources.**

***

## General permissions

The following list describes the permissions your **Atlassian** account used for integration with **Xopero ONE** must have for **Xopero ONE** to access, download, and back up all spaces and related resources in the selected **Confluence** instance.

### <mark style="background-color:blue;">User management</mark>

The **Atlassian** account must have the **app admin** and **user access admin** permissions.

### <mark style="background-color:blue;">Site permissions</mark>

The **Atlassian** account must have admin permissions to all **Confluence** spaces that are included in the backup.

### <mark style="background-color:blue;">Space permissions</mark>

The **Atlassian** account used for integration must be granted edit permissions for both open and restricted pages and blog posts.

{% hint style="danger" %}
Permissions in **Confluence** can be managed from multiple places, including per-space configuration. In **Settings** > **Users**, you can grant admin permissions to a specific user, but note that **app admin permissions in user management do not always provide access to all spaces**. The recommended approach is to manage permissions via **Organization settings** > **Permissions** > **Space management**.
{% endhint %}


---

# 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/confluence/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.
