In this page

Configuring Better Content Archiving for Confluence

This page discusses the configuration settings which affect the behavior of the app globally, regardless of which space it is used in or which scheme it is used with.

Global settings

You can configure these settings as a Confluence administrator, going to Confluence Settings (cog icon "⚙" in the top right) → Apps → Better Content Archiving → Global settings.

Data privacy (hiding the name of viewers and updaters)

The app allows you to hide the username of the last viewer and the last updater. These features aim to protect information that may be sensitive in certain teams (controlled by a corporate policy, for example).

The visibility of the last viewer and updater, as well as previous viewers and updaters, is managed through the "Data privacy" configuration setting. When enabled, the user interface displays the anonymized piece of text "undisclosed user" instead of the actual username:

The Content Status Indicator looks like this, when anonymized:

Another example is the User analytics tab of the Site dashboard, which looks like below, when anonymized:

The "Data privacy" configuration option affects the following user interface elements:

  1. Content Status Indicator
  2. Content Analytics (opened from the Content Status Indicator)
  3. Content Status Details (opened from the Content Status Indicator)
  4. Content List (displayed by the Content Status List macro or opened from the dashboards)
  5. User analytics on the Site dashboard and on the Space dashboard

Note that even when the usernames (sensitive) are hidden, the actual dates (not sensitive) are shown. Therefore, you can know that a page was last viewed 15 days ago, for instance, but you cannot know who was the viewer.

Enable purge automation actions

The app lets you configure automations that automatically perform actions on content at regular intervals based on specific criteria. One of the available automation actions is Purge, which permanently removes pages and blog posts.

To prevent accidental data loss, the Purge action is disabled by default. A Confluence administrator must enable it globally using this setting. Only then can it be selected in automations.

While this setting is disabled, any existing automations using the Purge action will be ignored, and you won't be able to configure new ones. If this occurs, you'll see a warning in the job execution log.

Allow archiving, deleting, or purging content that has children

By default, automation actions only apply to leaf pages, that is, pages that have no children. When this setting is enabled, automation actions may also be applied to pages that have child pages.

When an automation action is applied to a parent page, its child pages are automatically moved up one level. This is standard Confluence behavior and not a specific action performed by the Better Content Archiving app.

To prevent accidental changes to the page hierarchy, this setting is disabled by default. Note that this setting has no effect if the entire page subtree would be processed anyway. Its purpose is to prevent unprocessed content from being moved up in the page hierarchy.

Notify users when a scheduled job fails

Scheduled jobs may occasionally fail due to unexpected errors. This setting lets you select up to 10 users who will be notified by email when at least one scheduled job failed in the last 24 hours. Notification emails are sent daily around 1:00 AM UTC.

Questions?

Ask us any time.