At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Controlled terms | Review and approve governed meanings | Versioned terminology evidence | The organization owns the approved meaning |
| Confluence spaces and pages | Scan terminology usage | Findings, coverage, and usage evidence | Results depend on the selected scope |
| Approved scope | Create an enterprise freeze | Fixed meanings, revisions, hashes, and links | Coverage blockers remain visible |
| Deposited evidence | Search, verify, trace, and export | Audit and incident evidence | No certification, release approval, or signature execution |
How it works
- Configure Term Managers (RBAC).
- Create and approve governed terms.
- Run Compliance Scanner for the required spaces.
- Resolve findings and coverage gaps.
- Create an enterprise freeze for the controlled scope.
- Verify, trace, and export the deposited evidence.
Example
A regulated team changes the meaning of “material incident.” The app preserves the approved version, finds governed usage, freezes relevant page revisions, and shows connected evidence. Leaders can reconstruct the recorded decision without treating Confluence as the release or signature system.
What this does not mean
Compliance Glossary supports terminology governance and connected evidence. It does not provide legal advice, certify compliance, replace a QMS, approve releases, execute signatures, or create legal WORM storage.
Related questions
Next step
Evaluate the app with one governed space and one real terminology workflow.
View on Atlassian Marketplace