Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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 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.
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.
Recover Confluence spaces and groups from a backup copy, together with their resources and metadata.
Granular recovery for Confluence lets you restore selected spaces and related access settings without bringing back the entire instance, helping you recover only the data and permissions that matter while leaving the rest of the site unchanged.
The below steps demonstrate how to quickly restore Confluence spaces using GitProtect Management Service.
Open the Confluence tab (DevOps > Confluence), then click the Restore button next to the organization whose backup you want to restore.
You can also use the Explore button to restore your data.
Select the backup plan from which you want to restore data. Click the drop-down under Backup plans section and choose one of the plans from the list.
Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore button.
Select the destination for the recovery and click Next.
In the next aside, select the Restore Spaces option and click Next. Then, select spaces to restore and click Proceed.
Select the available data to restore and click Save to proceed.
In the Items to restore section at the top, you can change which of the previously chosen data you want to restore, if needed.
In the Restore to section, you can change the previously selected recovery destination if needed.
In Restore settings, you can add a custom suffix to restored space names and keys, and change the backup agent (default worker) that performs the restoration.
After defining all parameters, click the Restore button to begin the recovery process. When the process is complete, new space(s) will be created in the selected Confluence instance. You can monitor the restoration process in the Tasks tab.
The below steps demonstrate how to quickly restore Confluence groups using GitProtect Management Service.
Get into the restore view using the following method:
Open the Confluence tab (DevOps > Confluence), then click the Restore button next to the organization whose backup you want to restore.
Select the backup plan from which you want to restore data. Click the drop-down under
Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore button.
Select the destination for the recovery and click Next.
In the next aside, select the Restore Groups option and click Next. Then, select users to restore and click Proceed.
In the Items to restore section at the top, you can change which of the previously chosen groups and users you want to restore, if needed.
In the Restore to section, you can change the previously selected recovery destination if needed.
In Restore settings, you can choose whether to restore groups together with their users or restore only the groups. You can also add custom names to restored groups and change the backup agent (default worker) that performs the restoration.
After defining all parameters, click the Restore button to begin the recovery process. When the process is complete, new group(s) will be created in the selected Confluence instance. You can monitor the restoration process in the Tasks tab.
GitProtect allows you to select specific resources and metadata to restore — each element can be included or excluded by toggling the switch next to it.
Restoring never overwrites existing spaces in the organization — if you do not set a custom suffix for restored spaces and space keys, they retain their original names with automatically generated suffixes.
Restoring never overwrites existing groups in the organization — if you do not set a custom name for restored groups, they retain their original names with automatically generated suffixes.
Information about backup and recovery for Confluence instances.
Learn how to integrate Confluence with GitProtect to protect spaces and related resources.
Learn how to back up your Confluence resources with GitProtect.
How to quickly restore Confluence spaces and groups with GitProtect.
Learn how to back up your Confluence resources with GitProtect.
Overview of protected Confluence resources, including spaces, pages, and metadata secured by backup.
How to create a Confluence backup plan in GitProtect to configure automated protection for spaces and related space resources.
How to quickly restore Confluence spaces and groups with GitProtect.
Overview of the Confluence recovery process, including available restoration destinations and recovery options.
Recover Confluence spaces and groups from a backup copy, together with their resources and metadata.
How to create a Confluence backup plan in GitProtect to configure automated protection for spaces and related space resources.
Creating a Confluence backup plan in GitProtect enables administrators to define how and when Confluence data is protected within the backup environment. The configuration process allows defining backup scope, scheduling, and retention settings to ensure Confluence spaces, pages, and associated resources are securely stored and can be efficiently recovered when needed.
The following steps demonstrate how to create a Confluence backup plan using GitProtect Management Service.
Open the Backup tab (Plans > Backup) and click the + Add plan button in the top bar.
Select Confluence from the list.
Select the Confluence environment you want to include in the backup and how GitProtect will capture the Confluence data:
Protect all: protects the entire Confluence instance.
Select spaces: protects only selected spaces and related resources.
Set up a name for your backup plan.
In Data to protect section, click Edit to configure the data that you want to back up. Here, you can also change the default backup agent (worker), which is directly responsible for backing up your Confluence data.
Select one of the data stores assigned to your GitProtect instance to use as the backup storage.
Customize the scheduler and specify the retention period for your data.
Adjust the advanced settings, such as encryption, error handling, or bandwidth limit, to meet your organization's requirements.
Encryption: lets you secure your backup copy with encryption.
Compression: lets you compress and reduce copy size.
Review your configuration and click Save to create the backup plan, or Save&Run to start the first backup run immediately.
Exclude spaces: protects the entire Confluence instance except the selected spaces.
Set rules: captures data to protect based on the specified rules:
A Confluence backup based on rules defined by the space name behaves the same way as repositories in Git-type projects. For example, the rule git will match only the space with the exact name git. To create name-based rules, you can use the following wildcards:
* represents any number of characters. For example, the rule *git* will match spaces with names such as my-git-1, git, git-100, and similar.
? represents a single character. For example, the rule git-300? will match spaces with names such as git-3001, git-3002, and git-300m.
Error handling: allows you to specify how to handle potential backup operation errors. Includes an option to skip corrupted Confluence attachments during backup.
Bandwidth limit: allows you to reduce network usage and limit network speed during backup.
Backup scripts: enables configuring pre/post scripts executed during backup.
Task balancing: balances backup speed and CPU load.
Prevent system sleep: prevents your system from suspending while a backup is in progress.
Email notifications: lets you set up email notifications and its recipients.
You can deploy multiple agents and assign different agents to each backup plan.
Overview of the Confluence recovery process, including available restoration destinations and recovery options.
GitProtect provides a structured Confluence recovery process for protected resources, enabling restoration of content such as pages, spaces, attachments, and associated metadata to a selected recovery point. The recovery workflow supports granular restore scenarios, ensuring data consistency and minimizing downtime during incident recovery operations.
With granular recovery, GitProtect enables restoring selected Confluence content without a full environment rollback. You can target specific spaces or groups that were deleted or modified, and selectively restore only the content you need. This speeds up recovery, reduces operational disruption, and prevents overwriting healthy data.
Granular recovery is ideal when only a small portion of information needs to be restored. It’s especially useful when:
GitProtect provides two Confluence restore types:
Restore spaces — allows you to restore one or more spaces from a selected backup copy.
Restore groups — allows you to restore selected or all groups from a backup copy.
GitProtect allows you to restore Confluence backups in two ways:
To the original Confluence organization — restoring backups directly to the original organization.
To a new Confluence organization — restoring backups to a different Confluence organization*.
*The organization must already be integrated with GitProtect; adding a new organization during the recovery process is not supported.
Overview of protected Confluence resources, including spaces, pages, and metadata secured by backup.
Confluence protected resources define which parts of the environment GitProtect can access, backup, and restore.
The following list includes all Confluence resources covered by backup.