> 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 three sections:

* **Survey Form Labels** — titles, subtitles, field captions, and helper text.
* **Buttons & Navigation** — submit buttons, carousel controls (Back, Next, Skip, Finish), and similar actions.
* **States & Status Messages** — success messages, validation errors, and loading states.

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

Dynamic labels for custom form-builder fields (created in the survey editor) can also be translated — they appear automatically when those fields exist.

### 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.

### 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, field 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 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.meta-inf.hu/myra-master-your-ratings/use-myra/translation-studio.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.