Skip to main content

Localize property names

Localization properties translate the names your organization defines — most importantly custom property names — so users see them in their own UI language.

Prerequisites​

  • The Can Customize server permission.

Steps​

  1. Open Admin → Customization → Localization Properties.
  2. Add a property with its translations, or switch between the Language tabs to fill in each language's wording for existing properties. A brief Changes Saved message confirms each edit.

A property's name is fixed once created — only the per-language wording can change. If a property needs a different name, create a new one.

These translations are platform-wide. Which content languages a repository offers — and translating the content itself — is separate: see Working in multiple languages.

Other things localization properties drive​

Property names are the main use, but the same mechanism carries text elsewhere in the platform:

  • Email templates. Any notification template can reference a property as ${string.<key>}, resolved in each recipient's UI language. Quote a key that contains periods: ${string["my.custom.key"]}. This is also how you change an email's subject line — see Customize email templates.
  • Risk data-entry instructions. A property named igrafx.risks.instructions.<CATEGORY_ID> supplies the guidance shown on an ICS risk's Data tab — see Customize risk instructions.