Compliance Glossary for Confluence

Why is a glossary export not a baseline?

A glossary export is not an evidence baseline because it reports selected records, while a baseline fixes a versioned evidence state. The export supports review in CSV or a print-ready package. The baseline preserves approved meanings, exact document revisions, hashes, usages, findings, coverage, and trace relationships. It can then be verified and packaged as an archive.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Current terms, space, period, and declared scopeUse Audit Evidence Export and Generate Evidence PackageCSV and print-ready views of terms, approvals, histories, scan status, scan history, and finding resolutionsExport filtering uses the selected Confluence space, period, and 500-record evidence cap. It reports stored records at export time.
Baseline reason and selected spacesUse Terminology Baseline and Create baselineFrozen term states, scanned page references, page versions, usage rows, and comparison stateThis operational baseline uses stored scan evidence. A configured code cap is not proof of measured production capacity.
Governed spaces and retention policyUse Create enterprise freeze and Prepare and queue freezeFixed approved meanings, artifacts, revisions, hashes, usages, findings, coverage, and trace linksThe server pins one scan snapshot and checks capacity. Incomplete preparation does not create a promoted baseline.
Frozen manifest and stored evidenceUse Run verificationHash, count, object, index, usage, revision, and trace-endpoint resultsMissing, corrupt, stale, moved, unindexed, and unresolved evidence remain distinct. Verification does not repair data.
Completed baselineUse Export archiveBounded archive parts and a root manifestThe archive is a portable package. It does not create legal WORM storage or prove that the original source was correct.
A later term or page changeInspect Changed since baselineA delta from the frozen term or page stateThe completed baseline stays fixed. New work belongs to current state or a later baseline.

How it works

  1. Open Audit Evidence Export. Select Evidence scope, Period from, and Period to.
  2. Choose Generate Evidence Package. Use the CSV or print-ready output for a current review pack.
  3. Open Terminology Baseline. Select governed spaces and retention under Create enterprise freeze.
  4. Choose Prepare and queue freeze. Wait for Freeze progress to complete without unresolved coverage blockers.
  5. Review Frozen meanings and revisions. Choose Run verification.
  6. Choose Export archive when a portable, verifiable package is required.

Example

A bank needs a quarterly terminology report and a release evidence package. It exports the current glossary for reviewers. The CSV shows definitions, approval chains, scan status, and resolutions. For the release, an administrator creates an enterprise freeze. That baseline fixes the approved meanings and exact policy revisions used at the release point. Verification checks the package before archive export.

What this does not mean

The glossary export is useful for review, audit preparation, and human-readable evidence. It is not a frozen source package. A baseline preserves a defined state, but it does not certify compliance, approve a release, execute signatures, replace a QMS, or create legal WORM storage. Hashes detect change. They do not prove that captured content was correct or complete at its source.

Related questions

Next step

Use Audit Evidence Export for a current review pack. Use an enterprise freeze when the decision depends on exact meanings, revisions, relationships, and later verification.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.