At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Term Name and Definition | Select Save | Version 1 in Draft | An active license and term-manager access are required |
| Space, category, synonyms, owner, and dates | Store governed context | Scoped term record | A space sees approved terms in its effective glossary only |
| Draft term and change reason | Select Submit and confirm | In Review term | Submission does not approve the term |
| In-review term and approval reason | A separate eligible administrator selects Approve | Approved term and new version | Creator, editor, or submitter cannot approve the same content |
| Existing term and change reason | Select Edit, then Save | Updated version and History record | An approved edit does not automatically return to review |
How it works
- Open Compliance Glossary for Confluence.
- Select + New Term.
- Complete Term Name, Definition, and Space.
- Add ownership, review dates, synonyms, and notes when needed.
- Select Save.
- Select Submit and record the reason.
- Ask a different eligible administrator to select Approve.
- Use History to review recorded versions and reasons.
- Add the Compliance Glossary or Glossary term macro to a page.
Example
A legal team defines “Material incident” for its space. The owner adds the approved meaning, synonyms, and review date. Another administrator approves it. The Compliance Glossary macro then shows that meaning on Legal pages and in subscribed spaces.
What this does not mean
The app governs term records and their publication. It does not decide the correct legal meaning. Editing requires a reason and creates a version. However, editing an approved term does not automatically send it back to review. Teams that require reapproval must select Send for Review before the controlled change process.
Related questions
Next step
Create the first term, assign its scope, and send it to an independent reviewer.
View on Atlassian Marketplace