Watch: Freeze, Sign and Prove an Approved Document Package in Confluence (DORA Example)
The embedded player uses YouTube’s privacy-enhanced domain. You can also watch the video on YouTube.
Transcript
Release day. The auditor asks one simple question: what exactly did you approve? Which definitions, which documents, which versions? In most teams, answering that takes days of digging through pages and spreadsheets. In Compliance Glossary, you pick the spaces, write a reason, and create a terminology baseline. The app freezes every approved term with its meaning at that moment, together with every scanned page and its version. Now the accountable people sign it. Each sign-off records who signed, in which role, and when, bound to a fingerprint of the frozen content. For the auditor or your archive, download the baseline package as JSON or CSV: terms, meanings, pages, versions and sign-offs in one file. Six months later, the question has a one-click answer. Compliance Glossary for Confluence.
At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Approved terms and governed spaces | Create enterprise freeze | Fixed meanings and scanned page revisions with SHA-256 | Incomplete coverage remains visible under Coverage blockers |
| Supported files such as PDF, DOCX, or XLSX | Upload controlled evidence | File evidence in the current enterprise freeze | Supported types and a 25 MiB maximum apply |
| Code and tests | Declare trace node with an external reference | A candidate node that a second administrator reviews | No code revision, test result, or hash is captured |
| Approved trace links | Review them in Trace graph | Forward impact and Reverse provenance paths | Links are reviewed records, not frozen into the enterprise freeze. Candidate links do not count. |
| Terminology baseline | Create baseline, then Sign this baseline | Role sign-offs and Download baseline package (JSON) or (CSV) | A sign-off is not a qualified electronic signature |
| External approval reference | Declare trace node of type approval_evidence | Recorded reference to the external approval | Approval and signatures occur externally |
How it works
- Complete terminology review and the required scans.
- In Terminology Baseline, enter the Reason for this baseline, choose Spaces included, and select Create baseline.
- Collect role sign-offs with Sign this baseline.
- Download the package with Download baseline package (JSON) or Download baseline package (CSV).
- In Enterprise evidence workspace, use Create enterprise freeze and Prepare and queue freeze for the governed spaces.
- Resolve Coverage blockers, then select Run verification.
- Choose a Start node, select Show trace graph, and review Forward impact and Reverse provenance.
Example
A release changes a regulated term and the code that implements it. The freeze preserves the prior approved meaning, affected page revisions, and findings. Approved trace links connect the term to its requirement. The code change appears as a declared code reference node pointing to the repository. The repository and the external quality system retain the code revision, approval, and signature evidence.
What this does not mean
Compliance Glossary prepares and preserves supporting evidence. It does not capture source code, test runs, or code revision hashes. It does not decide release readiness, certify compliance, approve the release, or execute signatures. The organization owns the release decision and qualified approval system.
Related questions
Next step
Define the required release evidence before freezing the package. Keep code and test evidence in the systems that produce it.
View on Atlassian Marketplace