At a glance
| Area | Visible action | Result | Current boundary |
|---|---|---|---|
| Term governance | Use Terms, Submit for Review, Approve, or Deprecate | Status, owner, version history, change reason, and approval metadata | The last content editor cannot approve that content. |
| Bulk setup | Open Bulk Import Terms or Regulation Packs | Draft terminology records | One CSV import accepts 500 terms. Imported records still need review. |
| AI curation | Select undefined findings and choose Generate draft candidates | Editable draft proposals | An administrator starts the action. Generated content cannot approve a term. |
| Confluence scanning | Choose Scan Space in Compliance Scanner | Page status, findings, remediation records, and scan history | Results cover accessible pages reached by a completed scan. Automatic checks use page events and a debounce. |
| Finding handling | Choose Acknowledge, Justify, or Close | Status, owner, due date, severity, justification, and closure evidence | Justify needs text. Close needs closure evidence. |
| Page macros | Add Compliance Glossary or Glossary term | A glossary list or one inline definition | Macros show approved terms from the current space and subscribed source spaces. |
| Requirements mapping | Open Requirements Mapper | Required-term status, readiness counts, and cross-regulation definition conflicts | This maps catalogs to glossary terms. It is not a requirements execution system. |
| Cross-space use | Configure source spaces in Settings | Approved terms become available to a consumer space | Personal spaces are excluded from sharing controls. |
| Terminology baseline | Choose Create baseline | Frozen term states, scanned page references, changed-since results, and coverage warnings | Captures are bounded. The interface shows approved counts, truncation, and unsupported coverage states. |
| Enterprise freeze | Choose Prepare and queue freeze | A queued freeze with selected spaces, retention, source counts, and capacity checks | The server admits the job before processing. Coverage blockers remain visible. |
| Evidence workspace | Use Forward impact or Reverse provenance | Bounded trace results for the active baseline | Approved and imported links count as evidence. Candidate links remain separate. |
| Verification and archives | Use Run verification, Export archive, or Import archive | Verification results and portable archive processing | Export archive starts a server job. Browser import accepts JSON packages up to 10 MiB. |
| Downstream evidence | Choose Download glossary slice or Download reissue handoff | A JSON file for the selected retained artifact | The handoff records a requested external action. It does not perform that action. |
| GitHub findings | Enable Git Connector, set allowed paths, and choose Scan by request | Revision-bound terminology findings and job status | The connector is report-only. Source content and credentials are not shown in the interface. |
| Offline findings | Enable Offline Manifest Sync and choose Import manifest | Report-only findings from customer-generated JSON | The limit is 256 KB. Import does not connect a repository or change glossary terms. |
| File evidence | Choose Upload evidence with retention settings | Artifact and revision identifiers, usage count, and trace-candidate count | One allow-listed file may be 25 MiB. Parser depth depends on the file type. |
| Audit export | Open Audit Evidence Export and choose Generate Evidence Package | Terms, history, scan status, scan history, resolutions, and declared scope | Choose Download Evidence Package CSV after generation. Period and record caps bound the export. |
How it works
- Open Terms and create a definition.
- Move it from Draft to Review.
- A different eligible person selects Approve.
- Open Compliance Scanner and select a space.
- Choose Scan Space and review the saved page states.
- Resolve findings with the required human evidence.
- Choose Create baseline for a terminology snapshot.
- Use the enterprise workspace when revision hashes, traces, archives, or artifact-specific outputs are required.
Example
A policy team governs the meaning of “material incident.” A separate person approves the definition. The scanner then finds an older synonym on two pages.
Owners correct the pages and close each finding with evidence. The team creates a baseline and reviews changed-since results. It exports scoped audit evidence afterward.
What this does not mean
The global administration page is available to term managers. Page macros expose approved definitions in Confluence content.
The GitHub connector and offline manifest import require administrator enablement. Both produce findings for review. Neither changes governed terms automatically.
Enterprise actions sit under Terminology Baseline. Verification reads retained evidence. Archive export is asynchronous. Slice and handoff actions download JSON from the browser.
Evidence records support review and reconstruction. They do not determine legal compliance, approve a Confluence page, or approve a software release.
Related questions
Next step
Evaluate v6 with one governed space. Approve a term, scan its pages, create a baseline, and inspect the resulting evidence.
View on Atlassian Marketplace