Languages & Localization
Can each organization run the platform in its own languages — and its own terminology?
An organization registers the languages it works in, and the platform maintains a per-module catalog of UI text in each of them. The same catalog supports per-organization retexting — relabeling fields and screens in your own terminology, not just your own language.
Referenced across3 other parts of continON
How it works
Localization runs in two tiers. The first is the organization’s language registry — which languages exist for its users. The second is a per-module catalog of interface strings maintained in each of those languages, with bulk translation tooling so a new language is a managed job rather than thousands of individual edits. The catalog produces the resources the applications actually load.
Because the catalog is per organization, it doubles as a terminology layer. A company that calls a vacancy an open position, or a unit a branch, relabels those strings for its own users — the underlying records and logic stay identical while every screen speaks the organization’s language.
Localization does not stop at screen labels. Lookup values carry translated display text per language over stable internal keys, and notification and reminder messages resolve in the recipient’s language — so reference data and system messages localize along with the interface.
What the table carries
| # | Maintained | Resolved against it |
|---|---|---|
| 01 | Organization language registry | The set of working languages is per organization — registered once, offered to every user. |
| 02 | Per-module string catalog | UI text is cataloged per module and per language, with bulk translation for coverage at scale. |
| 03 | Retexting, not just translating | Relabel fields and screens in your own terminology while records and logic stay unchanged. |
| 04 | Lookups and messages included | Reference-data labels and notification messages localize through the same model. |
What this touches
See languages & localization running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.