Compliance Glossary for Confluence

Are pages scanned after edits?

Yes. Confluence page creation and update events start an automatic terminology check. The app first marks the older page result stale. It applies a five-minute per-page debounce and scans the current page. Findings stay within the page’s effective glossary. The app saves findings, approved usage, page version, and scan time. Failures remain logged.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Confluence page-created or page-updated eventRun the page-change handlerAutomatic check for that pageAn event without a page ID is ignored.
Existing resultMark it stale before reading the pageVisible stale state tied to the prior scanStale status is not a completed rescan.
Page scanned within five minutesApply the per-page debounceNo duplicate immediate scanThe prior result remains stale after a newer page version.
Current term cache and page bodyCheck governed terms and undefined candidatesFindings and approved-usage observationsResults use the glossary state available to the trigger.
Page space and subscriptionsFilter to the effective glossaryGlobal, local, and subscribed-source resultsTerms from unrelated spaces are excluded.
Completed checkSave page version, status, findings, usage, and timePassed or Needs attention in Space Pages StatusA trigger failure is logged and does not claim success.

How it works

  1. Create or update a Confluence page.
  2. The event marks its previous terminology result stale.
  3. If the debounce window allows, the app reads the current page.
  4. It checks the page against the effective glossary scope.
  5. Open Compliance Scanner and select the page’s space.
  6. Open Space Pages Status and select Refresh.
  7. Review Passed, Needs attention, Stale, or Not checked.
  8. Select Scan Space when a full manual reconciliation is required.

Example

An OPS page is updated with a deprecated global term, a deprecated LEGAL term, and an HR term. OPS subscribes to LEGAL but not HR. The automatic check records the global and LEGAL findings. It excludes the HR finding. Space Pages Status shows the saved result and page version.

What this does not mean

Automatic scanning is event-driven, not continuous. A page edited again within five minutes can remain stale until a later scan. Trigger failures are logged without interrupting the Confluence edit. Use Scan Space before relying on current space-wide coverage for an audit or baseline.

Related questions

What does the scanner check?How do I show that a page has no current findings?Can I compare scans over time?

Next step

After a controlled-document change, open Space Pages Status. Run Scan Space if the page is stale or not checked.

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