Compliance Glossary for Confluence

How do I prepare document reissue?

Start from the changed approved term and review Forward impact. Confirm each affected retained artifact, generate its glossary slice, and download a reissue handoff. The handoff gives the external document-control owner frozen meanings, usage evidence, archive context, and required actions. Approval, issuance, and signatures remain outside Compliance Glossary.

Last verified against production v6 · 24 October 2026
Baseline comparison and change note listing the changed term, its recorded reasons and changed pages
Compare two baselines and download the change note for controlled reissue. Staging demo data.

Watch: One Term Changed: Find Every Confluence Page It Affects

The embedded player uses YouTube’s privacy-enhanced domain. You can also watch the video on YouTube.

Transcript

A regulator updates a definition, or your legal team tightens one. One term changes, and someone has to find every document that uses it. In one of our industry interviews, a team had to reissue six hundred documents after a single change. Here is how that looks in Compliance Glossary. Edit the term. Because it is frozen in the current baseline, the app asks why, and records the reason. The new meaning goes back to review, and the person who edited it cannot approve it. Then look up its usage. Every scanned page that uses the term is listed, so you know exactly what to review. Freeze a new baseline and compare it with the previous one. You see which terms were added, changed or removed, with their reasons, and which pages changed. Download the change note, with the recorded reason for every change, and hand it to the people who reissue the documents. One changed term. A complete list of what it touches. Compliance Glossary for Confluence.

At a glance

InputActionOutputLimit
Changed governed termSelect Forward impactConnected approved artifactsMissing links can understate impact
Affected retained artifactSelect Download glossary sliceRelevant frozen meanings and usagesComplete indexing is required
Artifact and change contextSelect Download reissue handoffExternal action packageThe app does not edit or issue the document
External approval resultPreserve its referenceRelease evidence contextSignature execution stays external

How it works

  1. Approve the term change through the governed term workflow.
  2. Open the prior deposited baseline.
  3. Select Forward impact from the term.
  4. Review every affected retained artifact.
  5. Generate each artifact's glossary slice.
  6. Download the reissue handoff and send it to document control.
  7. Preserve the external approval reference with the release evidence.

Example

A definition change affects 18 controlled procedures. The team reviews the governed impact graph, then generates one glossary slice and handoff per retained procedure. Document-control owners revise and approve the documents in the external system. The next baseline captures the later approved state.

What this does not mean

The workflow scopes and packages evidence. It does not guarantee that every dependency is linked. It does not revise pages, approve releases, execute signatures, or replace document control.

Related questions

Next step

Complete impact review before sending any controlled artifact for reissue.

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