# Setup Translations

Use this section to set up translated S-Docs experiences and translated document output.

Start with the guide that matches your goal.

<table data-column-title-hidden data-view="cards"><thead><tr><th>Title</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Translate the S-Docs interface end to end</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/fwpDKtsSBGsC7th15OgR">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/fwpDKtsSBGsC7th15OgR</a></td></tr><tr><td>Translate document output end to end</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/eDuxlkQ4qy9j6eR5s5js">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/eDuxlkQ4qy9j6eR5s5js</a></td></tr><tr><td>Reference for translating the S-Docs interface</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/KwEZ1DFA86vUMCVtpUwV">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/KwEZ1DFA86vUMCVtpUwV</a></td></tr><tr><td>Reference for translating document content</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/dvVVMxYA7WIei0UzCIPq">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/dvVVMxYA7WIei0UzCIPq</a></td></tr><tr><td>Focused guide for merge fields, labels, and `toLabel()`</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/PMfuUiOzQuHHYrPGAXEh">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/PMfuUiOzQuHHYrPGAXEh</a></td></tr></tbody></table>

### Choose the right translation method

S-Docs translation has two layers.

* **UI translation** changes the S-Docs screens your users click through.
* **Document translation** changes the content inside generated output.

Use the document method that matches the value source.

* Use `translate="true"` for Salesforce-translated picklists and labels.
* Use `toLabel()` for picklist values returned by direct SOQL related lists.

### Quick decision guide

#### I need to translate the S-Docs interface

Use the UI translation guides.

That covers pages like **Generate Documents**, **Send Email**, and **Attach Files**.

#### I need to translate picklists or labels

Use Salesforce Translation Workbench.

Example use cases:

* picklist field values
* standard field labels
* translated custom field labels

#### I need translated related list picklists

Use `toLabel()` inside the SOQL query.

That tells Salesforce to return the translated picklist label instead of the raw API value.

### Common setup checklist

Before testing translations, confirm these basics:

* Translation Workbench is enabled when needed
* The template **Language** field is configured for Salesforce language codes
* Your test user is using the expected Salesforce language
* The translated field or value exists in the right system

### Recommended path

If you are starting fresh:

1. Translate the S-Docs UI if users need a localized generation flow.
2. Translate document content with Translation Workbench.
3. Add `toLabel()` for translated picklist values in direct SOQL related lists.
4. Test one language with one template before scaling out.

### Related topics

* [How to Work with Right-to-Left Languages](/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-work-with-right-to-left-languages.md)
* [How to Create Multilingual Documents](/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-create-multilingual-documents.md)


---

# Agent Instructions: 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:

```
GET https://help.sdocs.com/sdocs/advanced-template-logic/translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.