Building Blocks
Translations
Your own configuration in every language your people speak. Translate type names, field labels and workflow statuses once, with AI as a first pass and a reference language for your translators.
Updated Jul 25, 2026
Configuration · Building Blocks · 3.8
Gfacility’s own interface ships in several languages, but the things you name do not translate themselves. A ticket type called “Storing”, a custom field called “Kostenplaats”, a status called “Wacht op leverancier”: those are your words, and a colleague in another country sees them exactly as you typed them.
The Translations screen is where you give those words a version per language. It is a Building Block for the same reason classifications are: you set it up once, centrally, and every module that uses the term picks it up.
Why this matters to the business
"Our Polish colleagues get a Dutch dropdown"
The interface was translated, your type names were not. This is the screen that fixes it.
"People pick the wrong category"
A term someone half understands is a term they guess at. Guessed categories ruin reporting.
"A rollout to a new country stalls on wording"
Translate the existing configuration instead of building a second, parallel set of types.
"Nobody knows what still needs translating"
One list, filtered per language, shows the gaps instead of hiding them across ten screens.
What you can translate
The list is grouped by what the term belongs to, so you can work through one kind of thing at a time.
| Column | What it tells you |
|---|---|
| Type | Which kind of record the term comes from, so you can translate all ticket types in one pass. |
| Field | Which property is being translated: the name, the description, a label. |
| Workflow | For statuses, the workflow the status belongs to. The same word can mean something different in two workflows. |
Source language and reference
Pick a source language: the language your configuration was originally built in. It is shown next to each row as the reference for translators, so whoever fills in German is reading your original wording rather than a translation of a translation.
That single choice is what keeps a five-language setup coherent. Translate everything from the source, never from the nearest neighbour.
Translate with AI, then read it
There is a Translate with AI action that fills the gaps for you, with the model it used recorded alongside. Treat it as a first pass, not as the final answer: it is good at ordinary vocabulary and bad at your internal jargon, abbreviations and anything that is a proper noun in disguise.
Your changes are held until you save, so you can work through a batch and either save changes or discard changes as a whole.
Import and export
Export the list, hand it to a translation agency or a local colleague, and import the file back. The import merges: existing translations are updated and gaps are filled, so a partly completed file is safe to bring in and finish later.
Which decisions will you make?
Which languages do you actually support?
Every language you switch on is a maintenance commitment. Two done well beats six half done.
What stays untranslated?
Product names, building names and legal terms are usually better left alone. Decide this once and write it down.
Who signs off a language?
A native speaker who also knows the process. A correct translation of the wrong concept is still wrong.
When do you translate?
After the configuration is stable. Translating types you are still renaming is work you will do twice.