Define a term once. Confluence explains it everywhere.
Simple Glossary keeps one shared, multilingual glossary in Confluence Cloud and shows each definition right where the term is used.
- Free for all teams
- 80+ installs
- on Marketplace
Before we cut a , every open incident on the payment gateway needs a , and we have to be inside our for the quarter.
New checkout code ships behind a and goes out as a to 5% of merchants first. If the holds for 24 hours, the becomes the release.
Rolling back takes one switch: turn the flag off, then post what you saw in the payments on-call channel so the next shift has the full picture.
Readers get the definition without leaving the page
Before we cut a release candidate, every open incident on the payment gateway needs a postmortem, and we have to be inside our SLA for the quarter.
New checkout code ships behind a feature flag and goes out as a canary release to 5% of merchants first. If the error budget holds for 24 hours, the RC becomes the release.
Under the page title
The Glossary button in the page byline lists every term found on the page, with its definition. No extension needed. How it works
New checkout code ships behind a feature flag and goes out as a canary release to 5% of merchants first. If the error budget holds for 24 hours, the RC becomes the release.
If the canary shows errors, the flag is switched off and the on-call engineer opens an incident. Every incident on the payment gateway needs a postmortem before the next release candidate is cut.
The release manager confirms that we are still inside our SLA for the quarter and records the decision on this page.
On selected text
Select any text and choose Glossary to see the terms inside it. Editors can add a missing term from the same menu. How it works
New checkout code ships behind a feature flag and goes out to 5% of merchants first as a canary release.
If the error budget holds for 24 hours, the RC becomes the release. Otherwise the flag is switched off and the on-call engineer opens an incident.
Before the rollout continues, every open incident on the payment gateway needs a postmortem, and we have to be inside our SLA for the quarter.
Marked by the author
Authors can attach a term to a word by hand with the in-text term macro and choose how it looks. How it works
Everything else it does
Alternative forms
Other ways a term is written. A page that says “RC” still gets the definition of “Release candidate”. Learn more →
Labels
Group terms by topic, then filter the glossary page or a glossary table by label. Learn more →
Languages
A term can carry its name and definition in several languages. Each space chooses which ones it uses. Learn more →
Editors
The people allowed to add and change terms, chosen per space and for the global glossary. Everyone else reads. Learn more →
CSV import and export
Bring an existing word list in, or take the whole glossary out, as one file. Learn more →
Subscriptions
Follow a glossary and see what changed in it on your Confluence home page. Learn more →
From install to the first highlighted term
Install the app
Add Simple Glossary to your Confluence Cloud site from the Atlassian Marketplace.
Set up a space
In the space settings, choose the languages and who may edit terms.
Add terms
Write them on the glossary page or import a CSV file.
Turn on highlights
Optional. The Chrome extension marks terms in page text; the Glossary button and the macros work without it.
Download the extension or read the install guide.
Your glossary never leaves Atlassian Cloud
Simple Glossary is built on Atlassian Forge. Terms and settings are stored in Forge storage inside your own Confluence site. Nothing is sent to external servers.
The Marketplace listing carries the Runs on Atlassian badge, which Atlassian gives to apps that keep their data on its platform.
Read the security overviewFree for all teams.
For Confluence Cloud. Install it from the Atlassian Marketplace and add your first term today.