> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/managing-languages-and-translations-in-the-xyb-console.md).

# Managing Languages and Translations in the XYB Console

The XYB Console includes a fully integrated localisation solution that allows organisations to enable new languages, automatically translate content across services, and let users switch their preferred language instantly.

This article explains how localisation works from an end-user and administrator perspective.

### Who Can Use Localisation Features

Localisation features are permission-based. To manage translations and languages, users must have the relevant localisation permissions assigned by an administrator.

* **`plt-localise-svc/mfe_r`**\
  Grants access to the Localisation UI within the XYB Console.
* **`plt-localise-svc/localise_r`**\
  Allows users to view localisation keys and existing translations.
* **`plt-localise-svc/localise_w`**\
  Allows users to create, update, and manage localisation content and translations.

Users without the appropriate permissions will not see localisation-related menu items in the Console.

### Enabling a New Language (Admins)

Languages are enabled at the platform configuration level and automatically applied across all supported services and interfaces.

#### Steps to enable a new language

1. Go to **Product configuration > Services**
2. Select the **Product Configuration** service from the list.
3. Open the active **service version**
4. Navigate to the **Global Configuration** > **Languages** section
5. Add or enable the new language

Once enabled, the platform automatically starts generating translations for that language across all registered services. No manual translation work is required.

{% hint style="danger" %}
XYB does not supply the translation service directly. Customers are free to choose their preferred translation provider (for example, Google Gemini) and share the required API credentials with their XYB administrator for secure configuration.
{% endhint %}

### Automatic Translation Jobs

When a new language is enabled, the platform creates **translation jobs** that run in the background.

#### Where to view translation jobs

* Navigate to **Admin > Localisation > Jobs**

Here you can see:

* Job type (e.g. Language activation, Service registration)
* Status (Completed, In progress, Failed)
* Progress indicator
* Number of translated keys
* Creation timestamp

***

### Viewing Job Details and Progress

Clicking into a job shows detailed progress information.

#### Job details include:

* Target language
* Start time
* Overall job status
* Per-service translation batches
* Number of keys processed per batch

Each batch shows its current state (pending, completed, failed), making it easy to understand exactly what the system is doing at any point in time.

If a job fails, it can be **re-triggered** directly from the job details view.

### Translation Coverage Across the Platform

Once a language is enabled and translation jobs complete:

* The new language is available across **all supported Console modules**
* All micro-frontends automatically receive updated translations
* Newly registered services automatically inherit translations for enabled languages

This ensures a consistent, platform-wide language experience without manual coordination.

***

### Changing Your Language (End Users)

Individual users can change their preferred language at any time.

#### Steps to change language

1. Go to **Profile**
2. Open the **Language** dropdown
3. Select your preferred language

The interface updates immediately without requiring a reload or new session.

Your language preference is saved and applied automatically on future visits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xyb.co/xyb-console/managing-languages-and-translations-in-the-xyb-console.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.