> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/translation-studio.md).

# Translation Studio

## Translation Studio

Myra's **Translation Studio** lets you customize all customer-facing survey text in multiple languages — without changing your survey structure or field configuration.

Open any survey's settings and go to the **Translations** tab.

### Language packs

Each language pack holds the translated labels for one language.

* Select an existing pack from the language bar, or click **Add language** to create a new one.
* Set a display name and a BCP-47 language tag (for example `de`, `fr-FR`, `hu`).
* Clone an existing pack to start from another language's overrides.
* Delete packs you no longer need.

### What you can translate

Labels are grouped into these sections:

* **Survey Form Labels** — titles, subtitles, field captions, and helper text.
* **Buttons & Navigation** — submit buttons, carousel controls (Back, Next, Skip, Finish), and similar actions.
* **Field Validation Errors** — required-field and format error messages.
* **States & Status Messages** — success messages and loading states.
* **Survey Questions** — one field group per question configured in [Survey Builder](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/survey-builder.md), generated automatically: a **Question** label for every question, plus **Helper** (Number Pick), **Placeholder** (Text), and **Widget display text** for any question with a portal or help-center widget enabled. Fields are titled with the question's own text, so they're easy to find even with many questions.

Each field shows the English default. Edit a field to override it for the selected language; leave it blank to keep the default.

### Live preview

The preview panel updates as you type. Switch between **Respond** and **Success** states to see how the survey looks before and after submission. Click a label field to highlight the matching area in the preview — including jumping straight to a specific question when you edit one of its labels.

### Save and activate

* Click **Save changes** to persist your edits.
* Use the **Active** toggle on a language pack to control whether customers see that language on:
  * JSM portal survey forms
  * Public standalone survey pages
  * Website embed widgets

Only one language pack is active per survey at a time. If no pack is active, customers see the English defaults.

### Where translations apply

Translated labels are used everywhere the survey is rendered:

* Request panels on Jira issues
* JSM portal forms (including the multi-survey carousel)
* Public survey links
* Website collection popups and score widgets

{% hint style="info" %}
Translation Studio controls **text labels only**. Survey scope, question types, collection rules, and calculation strategy are configured on other tabs and are not affected by language packs.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/translation-studio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
