Compliance Glossary for Confluence

What does the scanner check?

The scanner checks governed Confluence pages for undefined terms, deprecated terms, unapproved governed terms, and configured non-preferred synonyms. It compares page content with the effective approved glossary for the selected scope. Results become page-linked findings and coverage evidence. A scan proves that recorded run, not permanent future compliance.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Selected Confluence spaceResolve its effective glossary scopeGoverned scan contextScope can include approved direct subscriptions
Page contentCompare observed terminology with governed recordsPage-linked findingsResults depend on indexed content and scan completion
Completed scanRecord coverage and findingsEvidence for that scan revisionLater edits can make evidence stale
Corrected page or termRun another scanNew current resultA resolved finding is not proof of future cleanliness

How it works

  1. Open Compliance Scanner.
  2. Use Select Space to Scan.
  3. Select Scan Space.
  4. Wait for the scan to complete.
  5. Review findings by page and type.
  6. Correct the page or governed term, then rescan.

Example

A policy page uses a deprecated term and one configured synonym. The scanner creates separate page-linked findings and points reviewers to the governed terminology. After correction, a new scan records the updated state.

What this does not mean

The scanner does not approve pages, certify compliance, or understand every business meaning. It reports supported terminology conditions in the completed scan scope.

Related questions

Confluence Undefined Term ScannerConfluence Terminology Finding ResolutionConfluence Audit Scope

Next step

Start with one governed space and review every finding type before expanding scope.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.