> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/how-to-guides/translate-a-mission.md).

# Translate a Mission

If your employees speak different languages, you can add translations to any Mission so they can complete it in the language they're comfortable with. Translations are entered manually — Taskmaverick doesn't auto-translate.

***

## Why translate Missions?

A hotel in Miami has housekeeping staff who speak Spanish and management who speaks English. The "Room Cleaning Checklist" is written in English, but half the team can't read it properly. Instead of creating two separate Missions, the admin adds Spanish translations to the same Mission. Each employee toggles to their preferred language on mobile.

{% stepper %}
{% step %}

### Enable the secondary language

Before you can translate anything, the secondary language must be turned on for your organization.

1. Go to [**Organization Settings**](/your-organization/organization-settings.md) **→ General Settings**
2. Enable **Secondary Language** 
3. Save

This adds translation fields throughout the [Mission Builder](https://documentation.taskmaverick.com/missions/how-to-guides/pages/bac3caf1d54e8f272f41bb96ccdf9524da1805b8#id-2.-content-builder) — they won't appear until this setting is on.
{% endstep %}

{% step %}

### Add translations to a Mission

1. Open any Mission in the Builder (new or existing)
2. You'll see **additional input fields** next to every translatable element
3. Enter the translation manually for each field

#### What can be translated

| Element                                | Where you translate it            |
| -------------------------------------- | --------------------------------- |
| **Mission Title**                      | Main Info section                 |
| **Guide** (instructions)               | Main Info section                 |
| **Alert**                              | Main Info section                 |
| **Question text**                      | Each question in the Builder      |
| **Response options**                   | Each answer choice in the Builder |
| **Divider titles**                     | Each divider in the Builder       |
| **Form Header** (Public Interface)     | Public Interface configuration    |
| **Completion text** (Public Interface) | Public Interface configuration    |

#### What is NOT translated

The Taskmaverick **app interface** itself (menus, buttons, navigation) stays in the primary language. Only Mission **content** is translated — the actual questions, instructions, and response options that employees interact with.
{% endstep %}

{% step %}

### How employees use it on mobile

When an employee [opens a Mission](/mobile-app/perform-a-mission.md#work-through-the-mission) that has translations:

1. A **language toggle** appears in the upper right corner of the Mission
2. Tapping it switches all Mission content to the secondary language
3. The employee completes the Mission in their preferred language
4. Responses are recorded regardless of which language was displayed

The toggle is per-Mission — switching language on one Mission doesn't affect others.
{% endstep %}
{% endstepper %}

## Good to know

* Currently only **some languages** are supported
* There is **no automatic translation** — every field must be translated manually by an admin
* The language toggle only affects **Mission content on mobile** — not the app interface, settings, reports, or web platform
* If a translation field is left empty, the employee sees the original language for that element
* Both [System Admins and Organization Managers](/your-organization/people.md#roles) can add translations
* Translations are preserved when a Mission is [duplicated](/missions/how-to-guides/shortcuts-and-useful-actions.md#duplicate-a-mission)


---

# 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://documentation.taskmaverick.com/missions/how-to-guides/translate-a-mission.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.