Revyz Command Center for Confluence
Revyz Command Center for Confluence
Breadcrumbs

Backup & Restore of Restricted Content

About this Page

This document explains how the Revyz app handles the backup and restore of restricted content. It covers the types of content backed up, what constitutes restricted content, how to enable its backup, and current limitations.

What is the Use Case?

The primary use case is ensuring total data coverage by extending your backup strategy to include restricted Pages and Blogs that standard Forge credentials cannot access. This allows administrators to maintain a secure, secondary copy of sensitive information while ensuring permissions are accurately synchronized during the recovery process.

Restoring Restricted Content

Watch the demo here on how to backup and restore restricted content using the Revyz app.


What Are the Types of Content That We Back Up?

Content Backup

The content that is backed up includes:

  • Pages

  • Blogs

  • Attachments (within the page and blogs)

  • Footer comments

  • Inline comments

The Revyz app uses Forge credentials for backing up content.

What Is Restricted Content?

  • A page is considered restricted if its sharing settings limit access to only a few people, instead of being "open to all". The same concept applies to blogs.

  • Once a page or blog is restricted, the attachments and comments within it also become restricted.

How to Enable Backup and Restore of Restricted Content

  • Restricted content cannot be backed up using only Forge credentials. To back up restricted content, you need an Atlassian API token.

  • Once the Atlassian API token is added, restricted content will be backed up during the normal backup process.

How to Set Up the API Token

Setting up the Atlassian API token

The Atlassian API token must be added in the backup settings. Either the organization admin or the site admin can add their token.

  • If the token has already been configured for configuration backups, you do not have to change anything for restricted content backup.

To learn how to set up an Atlassian API token, visit here. 

Limitations

1. Pages: Change in Status with Content Change

  • From Open to Restricted: If a Page is restricted without any changes made to the content, the new status will be reflected in the interface during the next content update.

2. Pages: Change in Status “Restricted to Open” without Content Change

From Restricted to Open: These changes in pages are detected and updated automatically.

  1. Blogs: Change in Status From Open to Restricted with Content Change

  • When a blog's status is changed to "Restricted" without modifying the content itself, it will be continued to be shown as "Open". The new permission level will synchronize in our interface upon the next content update.

4. Change in Status of Blogs from "Restricted" to "Open" without changing the blog content

When a Blog is moved from "Restricted" to "Open" (or vice versa) without modifying the actual content, the new status will be reflected in the interface upon the next content edit.

Note: If content in pages or blogs are modified at the same time the restrictions are changed, the new status is captured and updated instantly.