> For the complete documentation index, see [llms.txt](https://showreward.gitbook.io/showreward-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://showreward.gitbook.io/showreward-docs/getting-started/languages.md).

# Use ShowReward in English or Spanish

ShowReward separates the language of your dashboard from the language participants see.

| What you want to change                 | Where to change it                                 |
| --------------------------------------- | -------------------------------------------------- |
| Your own dashboard                      | **My profile → App language → Save changes**       |
| The project's participant portal        | **Settings → Lead portal language → Save changes** |
| Original campaign text and translations | Edit the campaign and open **Portal copy**         |

Changing language does not convert money or change reward amounts. Participants do not choose their own portal language; the project setting controls it.

[Tutorial 02](/showreward-docs/getting-started/project-settings.md#tutorial-02) covers the project portal language. The final chapters of [Tutorial 03](/showreward-docs/campaigns.md#tutorial-03) cover campaign copy and translations.

## Write original campaign content

In **Portal copy**, choose **Source content language** to match the language you actually use in the original fields. This covers the thank-you message, claim page message, terms, introduction video instructions and preparation video titles.

If your originals are English and your project's **Lead portal language** is English, you do not need a Spanish translation to launch in English.

## Add a translation manually

1. Fill in the original campaign content.
2. Under **English translation** or **Spanish translation**, enter the corresponding text beside each original.
3. For translated **Terms and conditions**, review the text and select **I have reviewed this translation of the terms and want to publish it when saving**.
4. Select **Save**.

Translated terms stay in **Draft awaiting review** until the review checkbox is selected and the campaign is saved. Editing those terms removes their publication until you review and save again.

If a translation is missing, out of date or unpublished, the participant sees the original text for that field. Changing original text invalidates that field's translation. Changing **Source content language** invalidates the previous translation direction.

## Request optional AI assistance

Select **Save and request translation** to save the campaign and queue a translation. You can also enable **Automatically translate source changes when saving**.

The status progresses through **Queued**, **Translating** and **Translation available**. It may take a few minutes. AI assistance preserves manual translations, and translated terms still require your review. If it reports **Translation failed; you can request it again**, retry or enter the translation manually.

Use the **English** and **Spanish** buttons in **Portal preview** to review both versions. The preview's language choice does not change the project's portal 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 by asking a question.

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

```
GET https://showreward.gitbook.io/showreward-docs/getting-started/languages.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.