In this page

Configuring Better Content Archiving for Confluence

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

All the global configuration options came with sensible defaults that work as expected in most cases.

Data privacy

Hiding the username of the last page viewer and updater

(since app version 8.1.0)

The app allows you to hide the username of the 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 the last updater is controlled by two independent configuration options. When those are activated, the user interface displays the anonymized piece of text "undisclosed user" instead of the actual username:

As another example, the Content Status Browser looks like this when anonymized:

These configuration options affect the following user interface elements:

  1. Content Status Inticator
  2. Content Status Browser
  3. Expired Pages list
  4. Not-viewed Pages list
  5. All notification emails

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.

The two features can be activated via the following standard Java system properties:

System property Description
carch.ui.hideLastViewer Set this to true to hide the username of the last viewer.
carch.ui.hideLastUpdater Set this to true to hide the username of the last updater.

Modifying these properties requires you to restart Confluence. For a detailed how-to, please see the Configuring system properties page in the official Confluence documentation.

Also, note that modifying system properties requires operating system level access to Confluence. It is extremely safe, as not even Confluence admins can re-enable the display of usernames or otherwise bypass the system property.

To verify if your custom values are correctly picked up, increase the logging level to DEBUG and you should see log lines like this:

2018-09-17 14:56:08,402 DEBUG [Long running task: Content Archiving [CARCH]] [archiving.service.persistence.GlobalSettingsManager] getPropertyValue System property <carch.ui.hideLastViewer> is set to true

Questions?

Ask us any time.