Translation overrides
Goal
Override or extend UI message keys per enabled language for this workspace (for example navigation labels), without changing business field translation maps (item names, party names, and other jsonb TranslatableInput values).
Who it is for
Anyone with localization.view can open the page and load overrides. Saving requires translations.manage.
Preconditions
- Localization is core (always available).
- At least one language is enabled under Localization setup — the language picker lists enabled languages only.
- Know the vue-i18n style Message key you want to override (placeholder example:
nav.dashboard).
Open the screen
Administration → Organization → Translation overrides (/translations).
Steps
- Choose Language.
- Review existing rows (Message key / Translation) or note No overrides yet.
- Add override for each key/value pair you need (values max length enforced by the API).
- Clear a value (empty string) to remove that override on save.
- Save — confirmation: Translations saved.
- Optionally review Calendar preview (today) (Stored ISO / Primary / Secondary) to sanity-check calendar display for the workspace.
Result
UI strings for that locale prefer workspace overrides. Catalog and master-data field translations are unchanged.
Hard stops
- That language is not in the supported-locale catalogue.
- Save blocked without
translations.manage. - Validation: overrides payload required; each value must be a string within the server max length.
Related
- Localization setup — enabled languages for the picker
- Tenant settings