A concept is one entry in a Glossary: a single idea that can hold a term (the actual text) in each of the Glossary's languages. This article covers the two ways to add a concept or term by hand — from the Glossary page, and from inside the Editor while translating — plus where bulk file imports fit in.
💡 Who is this for? This guide is for Project_Manager and Vendor who need to add new concepts and terms to a Glossary within the wxrks platform.
1. Adding a concept from a Glossary
In the sidebar, click Context, then Glossaries, and open the Glossary you want to add to. (If you haven't created a Glossary yet, see How to create a Glossary first — All about Glossaries covers how a Glossary's concepts, terms, and languages fit together.) On the Glossary's page, click Add Concept.
The Add Concept window opens with one term row already started:
Text — the term itself. Required.
Part of Speech — noun, verb, adjective, and so on.
Language — defaults to English (US) for the first term in a new concept; change it if you're starting in a different language. Required.
Click the arrow on the right to expand the row for more fields:
Case Sensitive and Forbidden — two independent switches; mark a term forbidden to flag it as one that should never be used.
Term Type and Gender — optional classification for the term.
Concept definition — shared across every term that belongs to this concept, regardless of language.
Usage and Note — free-text guidance for whoever uses the term later, such as where it applies or where it came from.
If the Glossary has Custom Attributes configured (set up when the Glossary was created — see How to create a Glossary), they appear here too.
Click + Add Term below the row to add another language's term to the same concept before saving — useful when you already know the term in two or more languages.
When you're done, click Publish to add the term straight to the Glossary, or Request to send it for review instead. A newly published term is set to Approved status by default. Whichever button you use, The Terminology Board covers what Publish vs Request actually does and how a requested term gets reviewed.
Adding a translation to an existing concept
To add another language's term to a concept that already exists, find its row in the Glossary's term table, click the ⋮ menu on the right, and choose Add Term:
An Add Term window opens for that concept, with the same term fields. Choose the language (only the Glossary's languages the concept doesn't have yet are offered), type the term, and click Save.
2. Adding a term from the Editor
You can also add a term without leaving a translation task. Select a word or phrase in the source text of a segment — this only works on the source side, not the target — and a GLOSSARY tooltip appears with an Add term button:
If nothing but No eligible glossaries shows up instead, the project has no Glossary linked with its Terminology Flow switch turned on — that switch, on the Glossary's own page, is what makes a Glossary eligible for this in-Editor flow.
Clicking Add term expands the form:
Source term and Target term — the selected text is pre-filled into one of these (matching whichever language you selected it in); fill in the other.
Part of speech and Term type (Acronym or Full).
Save to — choose All project glossaries to save to every Glossary linked to the project, or Specific to pick individual ones from a checklist.
Click Publish Term to add it directly, or Request Approval to send it to the Terminology Board — same choice as Publish/Request above. If the same term already exists, wxrks asks you to confirm before replacing it.
3. Importing terms in bulk
For adding many terms at once, use Import on the Glossary's page instead of adding concepts one at a time:
wxrks accepts .tbx and .xlsx files, and you can select several at once. A .tbx file exported from another terminology tool generally needs no extra preparation. A .xlsx file does need a specific column structure — see How to Format Your XLSX File for Glossary Import for the exact format.
Importing a term that already exists overwrites it only when it shares the same Term ID; otherwise it's added as a separate, duplicate entry.