> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/deploy/portal-base-project/portal-translations.md).

# Portal Translations

{% hint style="info" %}
Translation and Localization of the Developer Portal Application is available with the [**Security & Compliance**](/dev/the-security-module.md) module. Please contact <sales@form.io> for more information.
{% endhint %}

### Creating translations

In order to provide translations to the Portal application, you can add the translations using the **Language Resource** in the **Form.io Portal Base Project**. This resource has the following structure:

![](/files/jOgX3eQhlQyjt4D0V0gp)

Within this resource, we have the following fields:

* A Text Field called **Language**, which represents the language name.
* A Text Field called **Language code**, which is a shorthand alias for the language.
* A Data Map component called **Translations**, that has 2 fields: Text field for keys and one for translations.

A list of the keys can be found in the Translations JSON file, which is provided separately, where every chunk of text in the Portal Application is matched by a key with a meaningful name. By default, every key represents an English translation.

{% hint style="info" %}
Portal Translations are part of the Security Module. Please contact <sales@form.io> for more information to add this Module to your subscription and obtain the JSON file needed for Portal Translations.
{% endhint %}

You can create a new submission for each translation like the following screenshot, which illustrates a submission for Spanish language:

![](/files/bIJpc8Ud9aJw4ZhiDS8D)

Once you've created a submission in the Language resource, a new "language" is created. This is what will be used to manage all of the translations so you can now input the rest of your language translations the same way until you have multiple to chose from.

### Dynamic language switch

When you have multiple languages created, the **Language** switch dropdown appears in the navigation bar.

Here you can select any language from the list of languages you have configured. The currently selected language is highlighted as shown below.

![](/files/okqm5FGB6fhrjafZxRBt)

Selecting a new language will trigger a language change for all of the keys that were provided with translation in the submission for that particular language.


---

# 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://help.form.io/deploy/portal-base-project/portal-translations.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.