At a glance
| Input | App action | Output | Limit |
|---|---|---|---|
| Page content and the effective glossary | Scans the page with the glossary available to its space | Passed when the scan records zero findings | Applies only to the recorded Version and Glossary Revision |
| One or more recorded findings | Sets the page status from the finding count | Needs attention with the number under Findings | One result can contain several findings |
| A newer page version | Marks existing scan evidence as out of date | Stale | A new scan is required for a current Passed result |
| A listed page with no saved result | Adds a control row | Not checked | Zero under Findings is not a pass when the status is Not checked |
| Saved scan time | Displays when the evidence was produced | Last Scanned | The timestamp does not extend the result to later edits |
How it works
- Open Compliance Scanner.
- Choose a space under Select Space to Scan.
- Select Scan Space.
- Wait for Scan Complete.
- Open Space Pages Status.
- Find the page. Confirm Status is Passed and Findings is 0.
- Record Version, Glossary Revision, and Last Scanned with the result.
- Run another scan when the status is Stale or Not checked.
Example
The “Access Review Policy” page is scanned at version 12. The result contains zero findings. Its row shows Passed, Findings 0, Version 12, the scan’s Glossary Revision, and Last Scanned time. An edit creates version 13. The prior result becomes Stale. A new scan must pass before the page has current clean evidence again.
What this does not mean
Passed means the configured terminology checks found no issue in that scan. It does not prove semantic correctness, legal compliance, document approval, or permanent cleanliness. Definition-fit signals under Approved Usage remain separate. Scan errors cannot support Passed. They leave the affected page unconfirmed.
Related questions
Next step
Run Scan Space. Use Space Pages Status to confirm Passed against the recorded page and glossary revisions.
View on Atlassian Marketplace