# Translating the S-Docs App Menus

## What You'll Learn

In this tutorial, you'll translate the S-Docs user interface for one language and test it with a real user flow. By the end, you'll know how to:

* Import a prebuilt UI translation template
* Create custom UI translations manually
* Match S-Docs translations to Salesforce user language settings
* Test translated S-Docs pages end to end
* Troubleshoot missing or partial UI translations

## What You'll Build

A translated S-Docs user experience for one target language.

Your translated UI can cover:

* Generate Documents
* Edit Document
* Send Email
* Contact Lookup
* Attach Files
* Upload Files
* Mass Merge

**Estimated time:** 20 minutes

## Prerequisites

Before you start, make sure you have:

* Permission to manage S-Docs setup
* Permission to import S-Docs templates
* Permission to edit Salesforce user settings or test with a user who can change their own language
* One target language chosen, such as French, German, or Spanish

If you also need translated document output, see [Document Content Translation Tutorial](/quick-start/template-building/document-content-translation-tutorial.md).

{% stepper %}
{% step %}
**Step 1: Choose Your Translation Method**

S-Docs supports two ways to translate the UI:

* Import a prebuilt translation template
* Enter custom translations on the S-Docs Translation page

Use the prebuilt template when S-Docs already provides your target language.

Use custom translations when you need a language not provided out of the box, or when you want to adjust the wording.
{% endstep %}

{% step %}
**Step 2: Try the Fastest Option First**

If your language is available, start with the prebuilt template.

Download the matching translation package:

* [Translation Template: Spanish](https://kb.sdocs.com/wp-content/uploads/S-Docs-Translation-Spanish.zip)
* [Translation Template: German](https://kb.sdocs.com/wp-content/uploads/S-Docs-Translation-German.zip)
* [Translation Template: French](https://kb.sdocs.com/wp-content/uploads/S-Docs-Translation-French.zip)
* [Translation Template: Polish](https://kb.sdocs.com/wp-content/uploads/S-Docs-Translation-Polish.zip)
* [Translation Template: Japanese](https://kb.sdocs.com/wp-content/uploads/S-Docs-Translation-Japanese.zip)

After downloading the `.zip` file, import it with the S-Docs template migrator.

If your language is not listed, continue to the next step and build the translations manually.
{% endstep %}

{% step %}
**Step 3: Confirm the Imported Translation Was Added Correctly**

After import, locate the translation template record in Salesforce.

Check these settings:

* **Available for Use** is unchecked
* **Initially Visible** is unchecked

That is expected.

This record is not a document template. It only supplies translated S-Docs UI text.
{% endstep %}

{% step %}
**Step 4: Open the S-Docs Translation Page for Custom UI Translation**

Use this path when you want to create or edit translations yourself.

1. Open the App Launcher.
2. Search for **S-Docs Setup**.
3. Open **S-Docs Setup**.
4. Scroll to **Translate Data/UI**.
5. Click **Go To S-Docs Translation Page**.

This page lets you manage both UI translations and data translations.
{% endstep %}

{% step %}
**Step 5: Create or Select a Language**

On the translation page:

* Select an existing language if you already created one
* Or enter a new language name and create it

Use the same language naming consistently across S-Docs and Salesforce.

For example, if users work in French, use `French` consistently.
{% endstep %}

{% step %}
**Step 6: Enter UI Translations by Section**

In the **UI Translations** area, add translations for each section you need.

Common sections include:

* Generate Documents page
* Edit Document page
* Send Email page
* Contact Lookup window
* Attach Files window
* Upload Files tab
* Mass Merge interface

For each entry:

1. Read the English text on the left.
2. Enter the translated text on the right.
3. Continue through the page until each needed label is translated.
4. Click **Save**.

Start with the pages your team uses most often.

That usually means **Generate Documents**, **Send Email**, and **Attach Files** first.

{% hint style="info" %}
When you save a new language, S-Docs creates system translation template records automatically. Do not edit those records directly.
{% endhint %}
{% endstep %}

{% step %}
**Step 7: Set a Test User to the Target Salesforce Language**

S-Docs UI translation follows the user's Salesforce language.

To test the translation:

1. Open Salesforce Setup.
2. Go to **Users**.
3. Open a test user.
4. Set the user's **Language** to the target language.
5. Save.

If users manage their own preferences, they can change this in their personal settings instead.

Use a real test user whenever possible. That gives you the most accurate result.
{% endstep %}

{% step %}
**Step 8: Test the Main S-Docs Workflow**

Now verify the translated UI in the places users actually work.

Run this quick flow:

1. Open a record with S-Docs enabled.
2. Open **Generate Documents**.
3. Verify the page labels and buttons are translated.
4. Generate a document.
5. Open **Send Email**.
6. Verify the email page labels are translated.
7. Open **Attach Files** or **Contact Lookup** if your flow uses them.
8. Verify those labels are translated too.

If your team uses Mass Merge, test that screen separately.
{% endstep %}

{% step %}
**Step 9: Check for Partial Translation**

It is common to see a mix of translated and untranslated text during early testing.

If that happens:

* Go back to the translation page
* Find the untranslated section
* Add the missing entries
* Save again
* Refresh the test flow

Complete coverage usually takes one or two passes.
{% endstep %}

{% step %}
**Step 10: Fine-Tune the Wording**

After the first test, review the translated text with an internal user or native speaker.

Look for:

* Labels that are technically correct but awkward
* Terms that do not match your internal language standards
* Buttons or prompts that should use shorter wording

Update the translations and retest the same workflow.

Small wording changes can make the UI much easier to use.
{% endstep %}

{% step %}
**Step 11: Troubleshoot Common Problems**

Use this checklist when translations do not appear as expected.

**Nothing is translated**

* Confirm the test user's Salesforce **Language** matches the translated language
* Confirm you saved the translation entries
* Confirm the translation template was created successfully

**Only some labels are translated**

* Confirm you completed every relevant UI section
* Add any missing entries and test again

**Wrong language appears**

* Confirm the user is assigned to the correct Salesforce language
* Confirm your language naming matches expected Salesforce naming

**Imported translation does not seem active**

* Confirm you imported the correct language package
* Confirm you are testing with a user set to that language
  {% endstep %}
  {% endstepper %}

## What You've Learned

You now know how to translate the S-Docs UI with either a prebuilt package or custom translations.

You can now:

* Import supported language packs
* Create and edit UI translations manually
* Test UI translations with user language settings
* Refine missing or awkward translated text

## Next Steps

For deeper reference material, see:

* [Translating the S-Docs User Interface (UI)](https://github.com/kvantiem-sdocs/Quick-Start-Documentation/blob/main/advanced-template-logic/translations/translating-the-s-docs-user-interface-ui.md)
* [Document Content Translation Tutorial](/quick-start/template-building/document-content-translation-tutorial.md)
* [Translating Document Content in S-Docs](https://github.com/kvantiem-sdocs/Quick-Start-Documentation/blob/main/advanced-template-logic/translations/translating-document-content-in-s-docs.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/quick-start/document-generation/s-docs-ui-translation-tutorial.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.