Technical requirements for securing Confluence instances with custom domains.
Custom domains in Confluence allow organizations to use a branded URL instead of the default *.atlassian.net address. Even if a Confluence instance has a custom domain configured, proper protection requires adding the instance to GitProtect using the original Atlassian URL.
Confluence instances that use custom domains can be integrated with GitProtect, but must use their original Atlassian URL instead of the custom domain. This limitation results from how Atlassian identifies and authorizes organizations.
Atlassian security and administration APIs are bound to the organization's original Atlassian-managed URL (e.g., yourcompany.atlassian.net), not the custom domain. The custom domain serves as a user-facing alias for access and branding purposes.
Internally, Atlassian recognizes, authenticates, and grants permissions only through the original URL registered in Atlassian Administration (https://admin.atlassian.com). Therefore, GitProtect must use the original Atlassian URL to identify the organization and its applications, authenticate API requests, and enforce security and access controls.
Using the custom domain would prevent proper authorization and could lead to failed connections or incomplete protection, which is why the original Atlassian URL is required even when a custom domain is configured.
You can find organization's original URL in > Apps > App URLs > Custom domains > Actions > Show details.
The original URL is listed in the Details section under Default URL (fallback).
Learn how to integrate Confluence with GitProtect to protect spaces and related resources.
Required permissions for integrating Confluence with GitProtect and protecting its resources.
Technical requirements for securing Confluence instances with custom domains.
Learn how to integrate Confluence with GitProtect using an API token.
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.
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.
The Atlassian account must have the app admin and user access admin permissions.
The Atlassian account must have admin permissions to all Confluence spaces that are included in the backup.
The Atlassian account used for integration must be granted edit permissions for both open and restricted pages and blog posts.
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.
Learn how to integrate Confluence with GitProtect using an API token.
Adding Confluence to GitProtect allows organizations to secure business documentation and knowledge base resources against accidental deletion, data corruption, ransomware incidents, and configuration issues while supporting automated backup operations, granular restore capabilities, and long-term data retention management across cloud environments.
The below steps demonstrate how to quickly integrate Confluence with GitProtect using GitProtect Management Service.
For Confluence, use a classic token — GitProtect does not support scoped tokens.
Before adding Confluence to GitProtect, for all spaces you want to protect.
Open the DevOps tab on the left side of the window and select Confluence from the list.
Click the Connect button under Confluence Software.
In settings, enter the Atlassian organization address (for example, https://mycompany.atlassian.net) and add or select an API token from the Password Manager.
Configure the organization synchronization and the default worker. Specify the synchronization start time or set a time interval for automatic updates.
Click Proceed to complete the process of adding Confluence to GitProtect and granting it access to the specified resources.
Your Confluence instance has been successfully added to GitProtect. Click Custom policy to modify the backup policy settings, or click Run backup to start the backup immediately using the default policy configuration.
GitProtect can secure organizations that have a custom domain configured, but the organization must be added using its original URL, which can be found in > Apps > App URLs > Custom domains > Actions > Show details.
