> For the complete documentation index, see [llms.txt](https://helpcenter.gitprotect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.gitprotect.io/backup-and-recovery/confluence/integration/required-permissions.md).
# Required permissions
Required permissions for integrating Confluence with GitProtect and protecting its resources.
**Protecting Confluence in GitProtect 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 **GitProtect** must have for **GitProtect** to access, download, and back up all spaces and related resources in the selected **Confluence** instance.
### User management
The **Atlassian** account must have the **app admin** and **user access admin** permissions.
### Site permissions
The **Atlassian** account must have admin permissions to all **Confluence** spaces that are included in the backup.
### Space permissions
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 %}