At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Confluence page | Add the inline glossary macro | Configurable inline term | Author needs normal page-edit access |
| Approved effective term | Select it in macro configuration | Current definition for readers | Draft and deprecated terms are excluded as configured |
| Inactive app license | Read existing approved content | Continuity display | Administration remains blocked |
| Historical evidence need | Open a frozen baseline | Release-bound meaning | The live macro is not a historical snapshot |
How it works
- Edit the Confluence page.
- Insert the Compliance Glossary inline macro.
- Search the available approved terms.
- Select the required term.
- Publish the page.
- Open the term to confirm the visible definition.
Example
A procedure uses “critical supplier” in one control statement. The author inserts the inline macro for that approved term. Readers can open the governed definition without leaving the page. An earlier release still relies on its frozen baseline, not the current live macro.
What this does not mean
The inline macro displays current approved content. It does not create a term, record page approval, prove historical usage, or freeze the displayed meaning for a release.
Related questions
Next step
Use the inline macro when one governed term needs immediate reader context.
View on Atlassian Marketplace