# 4. How to Manage Languages and Translate CRM

Supporting multiple languages in your CRM ensures that users across regions can work in their preferred tongue and that customer‐facing elements display correctly. In **Settings > Configurations > Languages**, you control which languages are available for translation and which appear in the top‐level language selector. These settings work in concert with the **Translations** and **Texts** modules to provide a fully localized experience.

##### Use Cases

1. **Multi-Regional Teams:** Let support agents in Germany, Argentina, and Japan use the CRM in their local language.
2. **Global Customer Portals:** Ensure customer-facing emails, buttons, and notifications render in the end user’s language.
3. **Phased Roll-Outs:** Activate a new language only once all required labels, UI elements, and text blocks have been translated.

Languages and translations are managed in CRM through three sections:

1. Languages
2. Translations
3. Texts

##### Accessing the Languages Configuration

To translate CRM into another language:  
Navigate to **⚙️ Settings** in the sidebar, then select **Configurations**.  
Click the **Languages** tab at the top.

You will see two blocks:

1. **Available Languages** (to the left)**:** All languages available in our system.
2. **Active Languages** (to the right)**:** Languages that are used in your CRM.

##### Adding a Language to Active List

To add a language from the list of available languages to the list of active languages:  
In the **Available languages** panel, scroll or use the **Search** field to find your target language (e.g., “German,” “Japanese”).  
Check the box next to the language you wish to add. A flag or code (e.g., “Ar” for Argentine Spanish) appears to the right.  
Click **Save** at the bottom to apply the changes.

<p class="callout info">Note: The language will appear in the list of active languages, but will not yet be available for selection in the new menu. Before adding, it is recommended to translate CRM items into that language. Refer to the [\[How to Manage Translations\]](https://wiki.wi.services/books/wifox-business-core-solution-wbcs/page/5-how-to-manage-translations) and [\[How to Manage Texts\]](https://wiki.wi.services/books/wifox-business-core-solution-wbcs/page/6-how-to-manage-texts) for more information.</p>

##### Enabling a Language for Users

When you have all the necessary texts and CRM elements translated:

1. Go back to **Languages**.
2. In the **Active languages** panel, check the box next to the language you’ve translated content for.
3. (Optional) If you’d like this language to be the default for new users, click **Make as default** next to it.
4. Click **Save** again.

<p class="callout info">It will now appear in the top menu and be available for selection by all users.</p>

<article class="text-token-text-primary w-full" data-scroll-anchor="true" data-testid="conversation-turn-310" dir="auto" id="bkmrk-by-managing-availabl">By managing **Available** vs. **Active** languages, you control the rollout of new translations and prevent incomplete or partially-translated elements from going live. Always activate a language only after verifying that all UI labels (**Translations** module) and longer texts (**Texts** module) have been properly localized. This phased approach ensures a seamless, professional multilingual experience for both your team and your customers.

<div bis_size="{"x":143,"y":1341,"w":840,"h":89,"abs_x":729,"abs_y":1559}" class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)"><div bis_size="{"x":143,"y":1341,"w":840,"h":89,"abs_x":729,"abs_y":1559}" class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1"><div bis_size="{"x":143,"y":1341,"w":840,"h":89,"abs_x":729,"abs_y":1559}" class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn"><div bis_size="{"x":143,"y":1341,"w":840,"h":67,"abs_x":729,"abs_y":1559}" class="relative flex-col gap-1 md:gap-3"><div bis_size="{"x":143,"y":1341,"w":840,"h":22,"abs_x":729,"abs_y":1559}" class="flex max-w-full flex-col grow"><div bis_size="{"x":143,"y":1341,"w":840,"h":22,"abs_x":729,"abs_y":1559}" class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&]:mt-5" data-message-author-role="assistant" data-message-id="dfa2c8fa-b512-47d7-936f-b793bae8836c" data-message-model-slug="o4-mini-high" dir="auto"><div bis_size="{"x":143,"y":1341,"w":840,"h":22,"abs_x":729,"abs_y":1559}" class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">  
</div></div></div><div bis_size="{"x":143,"y":1363,"w":840,"h":22,"abs_x":729,"abs_y":1581}" class="flex justify-start">  
</div><div bis_size="{"x":143,"y":1386,"w":840,"h":22,"abs_x":729,"abs_y":1604}" class="mt-3 w-full empty:hidden">  
</div></div><div bis_size="{"x":143,"y":1408,"w":840,"h":22,"abs_x":729,"abs_y":1626}" class="absolute"><div bis_size="{"x":143,"y":1408,"w":840,"h":22,"abs_x":729,"abs_y":1626}" class="flex items-center justify-center">  
</div></div></div></div></div></article>