A glossary that works across every project

Every product has terms that must never drift: your brand name, your feature names, the words your users expect in their language. The glossary just grew up to protect them everywhere.

The problem

The glossary used to live inside a single project's settings. That made sense until you had more than one project, when the same brand term could drift between your web app and your docs. Terminology that is supposed to be a single source of truth could quietly fork.

What we shipped

The glossary is now organization-wide. Define a term once and it applies across every project automatically.

We also gave it a real home: it moved out of buried project settings into its own first-class page, with a cleaner table and a faster editing view. And it is no longer just a passive list. A new health check scans your translations and flags terms that are missing or translated inconsistently, so you can fix drift before it reaches users.

Behind the scenes, suggestions got smarter too: Localesy is better at inferring when a term in your glossary applies to the string it is translating.

How to use it

Open Glossary from your organization menu, add your key terms with their preferred translations, and run the health check. Anything off-glossary gets surfaced for review.

If you were maintaining glossaries per project, they are easy to consolidate, and you will only have to do it once.