At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Confluence page space | Add Compliance Glossary | Approved terms in the page’s effective glossary scope | Missing space context returns no terms. |
| Approved term record | Render the macro | Name, category, synonyms, definition, and notes | Draft, In Review, and Deprecated terms are excluded. |
| Reader text | Use Search terms… | Matches in names, definitions, and synonyms | Search covers terms already loaded into the macro. |
| More than one category | Use Filter by category | Terms in the selected category | The category control stays hidden when only one category exists. |
| Inactive app license | Read an existing macro | Existing approved terms remain visible read-only | Administrative workflows remain license-controlled. |
How it works
- Open a Confluence page in edit mode.
- Insert the Compliance Glossary macro.
- Publish or update the page.
- Confirm the header shows the expected approved-term count.
- Use Search terms… to find a name, definition, or synonym.
- Use Filter by category when the glossary contains several categories.
- Check the footer for the current space key and subscribed-source scope.
Example
An operations page belongs to the OPS space. OPS subscribes to the LEGAL glossary. The macro shows approved OPS terms, approved global terms, and approved LEGAL terms. It excludes an HR term because OPS does not subscribe to HR. A reader searches “incident” and sees the approved meaning and synonyms.
What this does not mean
The macro is read-only. It does not create, edit, submit, or approve terms. It does not show lifecycle actors or approval timestamps. It fails closed when the page has no valid space context. Use the administrator view for governance and audit evidence.
Related questions
Next step
Add Compliance Glossary to one governed page. Confirm its space scope and approved-term count before wider use.
View on Atlassian Marketplace