Skip to main content

Audit Library

The Audit Library lists all completed audit runs for your Confluence site. Use it to reload a prior run without rescanning, pin important runs for long-term retention, rename runs, or manage run lifecycle with trash and restore.

What's in the library​

The Audit Library displays all completed runs that have not been sent to trash. Each entry shows:

  • Run name — a custom name or the auto-generated default
  • Audit type — Spaces Audit, Permission Audit, or Content Audit
  • Completed — the date and time the audit finished
  • Run by — the name and avatar of the user who triggered the audit (or account ID if the user has been deactivated)
  • Pinned indicator — a filled pin icon if the run is pinned

By default, the library shows runs sorted newest first. You can filter by audit type, search by run name, or toggle to show only pinned runs.

Run naming​

When a new audit completes, it receives an auto-generated name in the format {audit type} YYYY-MM-DD — for example, Spaces Audit 2026-07-08. You can rename any run at any time to something more descriptive, like Q3 2026 Governance Baseline.

Renaming does not change the audit results.

Loading a run​

Click the eye icon to load any completed run. The results open in the same view as a live run — Audit Overview for summary and Audit Details for the full table. The loaded run remains active when you navigate between Overview and Details tabs.

Note: Snippets from a Content Audit are not available when loading from Audit Library — they are session-only and not stored. The app will display a note on the loaded run.

Pinning runs​

Pinning marks a run as important and prevents it from being automatically deleted. Pinned runs are excluded from the automatic retention purge and stay in the library indefinitely until you unpin them.

Use pinning for audit runs that serve as compliance evidence, governance checkpoints, or baseline records.

To pin a run:

  1. Click the pin icon (outline) on any run row.
  2. Enter or confirm the run name — a name is required to pin.
  3. Click Pin run.

Unpinning removes the pin protection but preserves the run name. The run will then be subject to the configured retention period and may be automatically deleted after the retention window expires.

Retention and trash​

All completed runs are retained for a configured period (default 60 days). At the end of the retention window, they are automatically purged along with all their results. Pinned runs are excluded from this automatic purge and remain until you unpin them.

Sending runs to trash​

To hide a run from the library immediately, use the trash action:

  1. Click the trash icon (delete) on any run row.
  2. Confirm the action in the modal. The message will show the effective retention period.
  3. The run is hidden from Audit Library and moved to trash.

Trashed runs are removed from view but their results are retained in trash for the configured retention period (same as non-pinned runs). You can restore a trashed run or delete it permanently at any time.

Managing trashed runs​

Navigate to Config (gear icon, far-right) and open the Trash Management tab to see all trashed runs.

The Trash Management view shows:

  • Run name — the custom name or auto-generated name
  • Audit type — Spaces Audit, Permission Audit, or Content Audit
  • Trashed — when the run was sent to trash
  • Trashed by — who sent the run to trash
  • Deletes in — how many days remain before automatic permanent deletion

From Trash Management, you can:

  • Restore — Return a run to the main Audit Library. Restore is non-destructive: it preserves the run name, pin state (if the run was pinned before being trashed), and all results. Click the restore icon (undo arrow).
  • Delete permanently — Remove a run immediately, bypassing the retention wait. This is irreversible and deletes all stored results. After confirming in the danger modal, the run and its results are gone.

Understanding deletion and retention​

If a trashed run is not restored or deleted manually, it will be automatically purged after the retention period expires. The retention period is configurable in Config → General Settings → Governance Thresholds under Trash Retention Days.

Important: If you lower the trash retention period, already-trashed runs become eligible for permanent deletion earlier (on the next daily automatic purge). Raising the period extends the grace period for runs already in trash. This is different from audit threshold settings, which apply only to future audits.

Run identity and profile lookup​

The Audit Library attempts to resolve user profiles to show display names and avatars for the "Run by" column. If profile lookup succeeds and the user's avatar is available, it appears alongside the name. If lookup fails (for example, if the user has been deactivated or the avatar is unavailable), the audit shows the account ID only.

Run identity and display data are never stored — they are fetched on demand each time the page loads.