At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Draft or review-stage term | Include its known identity in scan checks | Unapproved-term condition | The record must be known in the effective scope |
| Page content | Match the observed term | Page-linked finding | Scan scope and content availability apply |
| Governance decision | Approve, reject, or keep the term unapproved | Updated term state | Approval requires an eligible separate reviewer |
| Corrected page or approved term | Rescan | New recorded result | A prior scan remains historical evidence |
How it works
- Open Compliance Scanner.
- Select the governed space.
- Select Scan Space.
- Filter for unapproved-term findings.
- Correct the page or complete term review.
- Rescan and confirm the new state.
Example
A project page uses “critical service” while its definition is still under review. The scanner creates a finding. The team either removes the premature usage or completes independent approval. A later scan records whether the issue remains.
What this does not mean
A finding does not mean the draft definition should be approved. It shows that governed content and usage state are inconsistent. Review authority remains with the configured reviewers.
Related questions
Next step
Do not use governed terminology as approved before the review decision exists.
View on Atlassian Marketplace