What belongs in the glossary
A glossary term is any word or phrase that should always be translated (or not translated) in a specific, agreed-upon way:- Product and feature names — “Dashboard”, “Workspace”, “Smart Rules”
- Brand names — names that must never be translated or altered
- Technical identifiers — API concepts, UI element names, format codes
- Domain-specific vocabulary — industry terms with precise meanings that vary from the everyday sense
Organization-wide scope
The Glossary belongs to your organization, not to any individual project. Every term you define is available in all projects, and every Entri feature that uses terminology — the translation editor, AI translation, and content checks — reads from the same shared glossary. You define a term once and it propagates everywhere.Adding and managing terms
Navigate to Organization Settings → Glossary to create and manage terms.Create a term
Click Add Term and enter the source-language text. This is the term as it appears in your source strings.
Add translations
For each target language your organization uses, enter the approved translation. Leave a language blank if no approved translation exists yet.
Term options
Each glossary term has several options that control how it behaves:Do not translate
Mark a term as Do not translate to tell translators and the AI to pass it through verbatim. Use this for brand names, trademarks, and technical identifiers that should never be localized. When AI translation encounters a “do not translate” term in a source string, it copies the term unchanged into the target output.Case sensitivity
By default, glossary matching is case-insensitive — “dashboard”, “Dashboard”, and “DASHBOARD” all match the same term. Enable Case sensitive on a term when capitalization carries meaning and you only want to match the exact casing you specify.Part of speech and notes
The Part of speech field (noun, verb, adjective, etc.) gives translators grammatical context — especially important for languages where the correct translation depends on how the word is used in a sentence. The Notes field is a free-text area for anything else: usage examples, links to style guide sections, or explanations of why a particular translation was chosen.Glossary checks
The glossary is not just a reference document — it actively checks your content. The Glossary Check scans your translations and flags any string that contains a recognized source term but uses a different target translation than the one defined in the glossary. This catches:- Translators who are unaware of an approved term
- Inconsistencies introduced when different translators work on the same project
- AI-generated translations that deviated from the approved vocabulary
AI translation integration
When you run AI Translation, Entri automatically includes your full glossary in the prompt. The AI receives:- Every source term and its approved target translation for the requested language
- Which terms are marked “do not translate”
- Term notes, giving the AI additional context about usage
Example glossary structure
| Term | Part of speech | Do not translate | Notes |
|---|---|---|---|
| Entri | Noun | Yes | Brand name, never translate |
| Translation Memory | Noun | No | Capitalize both words in all languages |
| Workspace | Noun | No | Refers to the top-level org container |
| Smart Rules | Noun | No | Product feature name, capitalize |