Translations

Feature ID: FU-1063

Document Version: 1.0

Date: 23-12-2025

1. Introduction

The Language Translations feature in Unifize enables organizations to localize the platform language for global teams. With support for 27 languages, users can interact with Unifize in the language they are most comfortable with, improving adoption, accessibility, and day-to-day usability.

Language Translations consist of three core elements:

• Primary Language – the default language of the Org and the source of truth for all translations.

• Supported Languages – additional languages available for users.

• Preferred Language – the individual user’s preferred language, configurable from their profile.

Admins can further fine-tune the organization’s language experience using the Translation Editor, which allows editing auto-translated UI text, form fields, section labels, dashboard titles, and more.

Below are the main capabilities of the Language Translations feature on Unifize platform:

• The feature allows organizations to configure a Primary Language, which acts as the source of truth for all application text and custom fields and becomes the default language for all users whose preferred languages are not supported by the Org.

• Admins can enable multiple Supported Languages from the list of 27 available languages, allowing users across global teams to interact with Unifize in the language they are most comfortable with.

• Each user can independently choose a Preferred Language from the Preferences section, to ensure that their interface is displayed in the language they prefer without affecting other users in the Org.

In Unifize, all language-related capabilities are controlled by admins. Users can only select from the languages that admins have explicitly made available.

This means:

• Users can only change their interface language by going to Profile → Preferences → Language, but only languages enabled by admins will appear in this list.

• Admins manage all language features, including which languages are supported and all translation editing, through Profile → Org Settings → Translations. If given permission, users can also see and edit the Translations page in the Org Settings.

Note: Users do not have permission to enable languages or edit translations unless an admin grants these permissions explicitly.

Admins must clearly understand how the three layers of language behavior work, because the system's translation logic depends on them.

1. Primary Language

• The Primary Language is set during the Org creation.

• It becomes the source of truth for all application text, custom fields, and system labels.

• This language cannot be changed later.

2. Supported Languages

• Supported Languages are the languages your Org chooses to make available to end users.

• Unifize offers 27 languages. Your Org may enable any number of languages depending on its requirements. List of 27 languages supported by Unifize:

  • English (Primary language

3. Preferred Language (User-Level Behavior)

• Each user selects their Preferred Language from Profile → Preferences → Language.

• Users see the UI in their selected language, independent of other users.

• If not set:

Language Translation features are permission-controlled to ensure only authorized users can manage edits.

1. Navigating to Permissions

1. Inside Org Settings, click Role Management.

2. Each role contains permissions that determine what users can and cannot do. Two permissions relate specifically to language translations:

• View Translation – allows users to view the “Translations” feature inside Org Settings of Profile.

• Edit Translation – allows users to view and edit the “Translations” feature inside Org Settings of Profile.

2. Permission Behavior

• Admins have both permissions enabled by default.

• Org Members and External Users do not have these permissions unless manually granted.

• When Edit Translations is enabled for a role, View Translations is automatically granted.

Admins should ensure that only trusted users or regional translation owners receive edit capabilities due to the global impact of translation changes.

Admins and org members can edit the translated language for the platform if they want to modify any translated content. This can be accessed by the following steps:

1. Go to Org Settings.

2. Click Translations in the left navigation.

3. At the top of the editor, a dropdown allows you to choose which Supported Language you want to view or edit. All translation operations will apply to the language selected here.

Translations can be grouped by areas of the application by clicking on the “Choose the area” tab and selecting which area of the platform content you want to filter. The Translation Editor provides structured filters, such as:

• Homescreen

• Processes

• Forms

• Dashboards

A search bar is available to quickly locate:

• Field labels

• Dashboard names

• Section titles

• Button text

Admins can type partial matches or keywords to identify exactly which UI strings need to be updated.

After editing translations, admins should ensure that updates appear correctly in the user interface.

Validation Steps:

1. Go to Profile → Preferences → Language.

2. Select the language you edited.

3. Navigate through the platform to verify:

Language selection at the user level is limited to choosing a Preferred Language from the list of languages that admins have enabled for the organization. Users do not have permissions to add new languages, enable translation functionality, or modify translated text.

Admins fully control:

• Which languages appear in the user dropdown

• Whether translations are available

• The quality and accuracy of translated UI labels

Users only consume what admins have configured.

Users can update their personal language preference by following the steps below:

1. Click the Profile Icon in the top-right corner of the platform.

2. Select Preferences from the dropdown.

3. Open the Language tab inside the Preferences modal.

This setting impacts only the user who changes it. Other users in the Org continue to see the interface in their own selected or default languages.

If the user does not select a Preferred Language manually:

• The system checks the user’s Operating System language.

  • If the OS language is part of the Org’s Supported Languages, the platform uses it.

• If the OS language is not supported, the platform defaults to the Org’s Primary Language.

This ensures a predictable and consistent language experience, even without user input.

Once a Preferred Language is selected, the user will see translated versions of:

• Navigation menus

• Buttons and toolbars

• Dashboard components

• Custom field names and descriptions

Users will only see translations that admins have approved or edited in the Translation Editor.

Certain elements always remain in their original language, regardless of user selection:

• Conversation messages

• Uploaded documents and file previews

• Process titles

• Checklist field values entered by users

This ensures that critical identifiers, user-generated content, and file data remain unchanged.

• Only languages that admins have explicitly enabled for the Org will appear for users. Users cannot enable additional languages on their own, which means any required language must first be coordinated and configured by an admin.

• The Primary Language of the Org cannot be changed after Org setup, which limits the ability to restructure translation foundations later and requires careful consideration before initial configuration.

• The Translation Editor does not support translation of user-generated or dynamic content, such as conversation messages, uploaded documents, file previews, record titles, process titles, and checklist values entered by users.

• Admins should enable Supported Languages only after confirming they are needed by active user groups, to ensure the translation workload remains manageable and aligned with real usage.

• All translation edits should be reviewed systematically using the progressive filters and search capabilities in the Translation Editor to maintain consistency across processes, dashboards, and system labels.

• It is recommended to assign translation responsibilities to a designated admin role or regional reviewer, rather than distributing permissions widely, to maintain quality control and reduce inadvertent inconsistencies.