Skip to main content

Configuration

Configuration is where Confluence administrators set governance policies that apply across all audit runs. Instead of managing audit parameters per run, you configure them once, and every scan respects your site's policies.

What you can configure​

Governance Thresholds

Set the age limits that determine what the app flags as stale:

  • Content age threshold — Pages not updated within this many days appear as stale in Content Audit.
  • Space inactivity threshold — Spaces with no page updates in this many days are flagged as inactive.
  • Trash retention — How long the app retains deleted audit runs before permanent deletion.

Risk Vocabulary

Define keyword categories that the Content Audit scan uses to identify content risk. The app comes with three built-in categories (Credentials, Personal Data, Financial), which you can customize or expand. You can:

  • Add, edit, or delete categories.
  • Add or remove keywords within each category.

Scan Options

Control whether Content Audit results include matched text snippets (the surrounding sentence for each keyword match).

Trash Management​

The Trash Management tab is where you manage audit runs you've sent to trash. You can:

  • View trashed runs — See which runs are in trash, when they were deleted, and how many days until permanent removal.
  • Restore a run — Move a run back to the Audit Library without permanently deleting it.
  • Delete permanently — Remove a run and all its data immediately, rather than waiting for automatic purge.

The app automatically removes trashed runs after the retention period you set in Governance Thresholds (default: 60 days).

Who can access Configuration​

Only Confluence administrators can view or edit Configuration. The Configuration tab appears only if you have the "Confluence Administrator" permission.

How configuration affects audits​

Configuration settings apply prospectively — to new audit runs you create after saving changes. Existing audit results are not recalculated if you adjust a threshold. This keeps your audit history stable and audit-comparable over time.

If you change the content age threshold from 365 days to 180 days, for example, a page that was flagged as "stale" in a previous run may no longer match the new threshold — but the previous run's results don't change. Only the next Content Audit scan uses the new 180-day limit.