At a glance
| Record | Visible in Space Scan History | Retained detail | Limit |
|---|---|---|---|
| Saved page scan | Date | Scan timestamp | A failed scan does not create a completed snapshot. |
| Findings for that page scan | Findings | Full finding count | The count is not a space-wide total. |
| Unique flagged terms | Terms Flagged | Term-name summary | The retained summary is capped at 50 names. |
| Scan context | Not shown | Page ID, page version, glossary revision, and page status | The history table cannot confirm like-for-like scope on its own. |
| More than 20 returned snapshots | Showing latest 20 of _n_ scans. | The history request defaults to 100 records | Only 20 rows appear in the table. |
| Invalid term summary | Summary unavailable | The finding count remains visible | The affected term names cannot be read from that row. |
How it works
- Open Compliance Scanner.
- Use Select Space to Scan.
- Select Scan Space when current results are required.
- Open Space Scan History.
- Review Date, Findings, and Terms Flagged.
- Treat each row as one saved page scan.
- Use an evidence export when analysis needs page ID, page version, or glossary revision.
Example
A leader sees three rows with 12, 4, and 9 findings. Those values can come from different pages. They can also reflect different page or glossary revisions. The screen confirms that scans were recorded and shows their summaries. It does not establish that terminology exposure fell and then rose across the whole space.
What this does not mean
Space Scan History is suitable for a quick review of recent scan activity. It is not a chart, a space-run aggregate, or a causal analysis. It does not show page names. A sound trend comparison needs stable scope and the retained page ID, page version, and glossary revision. The evidence export includes those fields for each scan-history row.
Related questions
Next step
Open Space Scan History for recent activity. Export the scan records before making a trend claim.
View on Atlassian Marketplace