At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected Confluence space | Resolve pages and effective glossary | Initial scan scope | Access and pagination affect coverage |
| Empty effective glossary | Analyze observed candidate wording | Undefined candidate terms | Candidates can include noise |
| Existing governed terms | Check supported terminology conditions | Page-linked findings | Results depend on configured data |
| Completed scan | Store scan identity and coverage | Baseline for later comparison | It is not permanent future status |
How it works
- Open Compliance Scanner.
- Use Select Space to Scan.
- Select the initial governed space.
- Select Scan Space.
- Review coverage and findings.
- Curate useful candidates as drafts, then rescan after approval.
Example
A new governance space has no approved terms. The first scan records which pages were processed and surfaces recurring candidate wording. A manager discards noise, creates two drafts, and sends them for independent review. A later scan uses the approved glossary.
What this does not mean
First-run candidates are suggestions from observed content. They are not authoritative definitions, legal advice, or approved terminology. Human curation and review remain required.
Related questions
Next step
Review first-run candidates before adding any of them to the governed glossary.
View on Atlassian Marketplace