At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Governed term | Match it within the effective glossary scope | Term identity used by the scan | Scope can vary by space subscriptions |
| Page revision | Record approved usage observations | Page-linked usage evidence | Later edits can make the result stale |
| Completed scan | Bind usage to scan and glossary revision | Reproducible observation context | Scan completion and coverage matter |
| Enterprise freeze | Deposit selected usages with exact evidence | Frozen release-bound usage records | Only captured scope enters the baseline |
How it works
- Approve the governed term.
- Run Compliance Scanner for the required space.
- Open the page status or usage evidence.
- Confirm the page and glossary revisions.
- Review coverage and stale-state indicators.
- Freeze the usage evidence when release-bound proof is required.
Example
An auditor asks where “critical supplier” appeared at release time. The deposited baseline links the approved meaning to recorded page usages and exact revisions. Pages outside the selected scope remain outside that claim.
What this does not mean
Usage proof is bounded by scanned content, access, indexing, and selected baseline scope. It is not arbitrary full-text search and cannot establish use in unavailable sources.
Related questions
Next step
Check scope and revision identity before presenting term usage evidence.
View on Atlassian Marketplace