Compliance Glossary for Confluence

How does term review work?

A term manager selects Submit and records a reason. The term moves from draft to review. Another eligible term manager selects Approve or Reject. Approval is blocked for the creator, submitter, or last content editor. Every transition creates a new version with actor, time, status, and reason before the current term is updated.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Draft termSelect Submit and enter a reasonStatus changes to reviewDraft cannot move directly to approved
Term in reviewSelect Approve and enter a reasonApproved term with approver and approval timeCreator, submitter, updater, or content editor cannot approve
Term in reviewSelect Reject and enter a reasonTerm returns to draftRejection does not delete the term
Decision contextAdd Communication evidenceOptional audience, channel, date, or evidence referenceField is limited to 2,000 characters
Loaded term versionSubmit the expected versionConflict-safe status updateA concurrent change requires reload before another decision
Status transitionWrite the audit version before the entity updateVersioned actor, time, status, and reasonIf audit writing fails, the status does not change

How it works

  1. Open Terms.
  2. Filter by Draft.
  3. Select Submit for the required term.
  4. Enter Reason for submission. Add Communication evidence when relevant.
  5. Select Confirm.
  6. A separate term manager filters by In Review and selects Approve or Reject.
  7. Record the decision reason and select Confirm. Use History to open Version History.

Example

An author creates “Risk owner” and submits it with the reason “Ready for policy review.” A separate term manager checks the definition. The reviewer records “Matches the approved policy wording” and selects Approve. The app stores a new approved version with the reviewer and time. The original author cannot approve the same term.

What this does not mean

Term approval governs glossary content. It does not approve a release. It does not execute an electronic signature. It does not certify compliance. Reject returns the term to draft. Approval does not freeze an evidence baseline. That requires a separate enterprise freeze and verification workflow.

Related questions

Next step

Submit one draft term and have a separate term manager record the decision.

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