# Translating User Interface
## What is S-Docs UI Translation?
S-Docs UI translation allows you to translate the entire document generation experience that your employees interact with inside of Salesforce. This includes the pages where users select templates, generate documents, send emails, and use other S-Docs features. Translating the UI ensures that multinational teams can work efficiently in their preferred language.
## How is UI Translation Used in S-Docs?
For businesses with multinational employees who need to generate documents, translating the S-Docs user experience can be imperative to allowing them to work as efficiently and seamlessly as possible. S-Docs allows you to translate the entire document generation workflow, from selecting templates to sending emails.
**Translatable S-Docs pages include:**
* The Generate Documents page (where templates are selected and generated)
* The Edit Document page (where generated documents can be edited using Live Edit)
* The Send Email page
* The Contact Lookup window (appears when users click inside the Contact/User Lookup field)
* The Attach Files window (appears when users click Attach or Remove Files)
* The Upload Files tab within the Attach Files window
* The Mass Merge interface
**Note:** Currently, the S-Docs template editor is only available in English. However, fields listed in the Insert Field menu will appear in the user's Salesforce language.
***
## Translation Methods
S-Docs provides two options for translating the user interface:
1. **Download pre-configured translation templates** provided by S-Docs
2. **Define your own custom translations** on the S-Docs Translation page
***
## Method 1: Download Pre-Configured Translation Templates
S-Docs provides ready-to-use translation templates for several languages that you can import immediately.
### Step 1: Import a Translation Template
Click the link below to download your desired language template as a .zip file:
* [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, use the S-Docs template migrator to import the template into your org.
### Understanding Translation Templates
When imported, the translation template record will have the following settings:
* **Available for Use**: Unchecked
* **Initially Visible**: Unchecked
These settings are intentional—this is not a template for document generation; it simply provides the translation for the S-Docs user experience.
### Step 2: Configure the Translation
After importing the translation template, the S-Docs UI will automatically be available in the translated language for users whose Salesforce language settings match the translation language.
***
## Method 2: Define Your Own Custom Translations
If you want to define your own translations or translate to a language not provided by S-Docs, you can manually create translations on the S-Docs Translation page.
{% stepper %}
{% step %}
#### Step 1: Navigate to the S-Docs Translation Page
1. Click the App Launcher
2. Type "S-Docs Setup"
3. Click "S-Docs Setup" in the dropdown menu
4. Scroll down to the "Translate Data/UI" section
5. Click "Go To S-Docs Translation Page"
{% endstep %}
{% step %}
#### Step 2: Choose or Create a Language
**If You've Previously Defined Translations:**
1. Choose the language from the dropdown
2. Click to edit the existing translations for that language
**For New Languages:**
1. Enter the name of the language in the text field
2. Click "Define new translations for this language"
{% endstep %}
{% step %}
#### Step 3: Define UI Translations
The S-Docs Translation page is divided into two sections:
1. **UI Translations**: Translates the S-Docs interface that employees interact with inside Salesforce
2. **Document translation settings**: Stores translation settings used by document output guidance
**UI Translation Structure**
UI Translation options are organized into sections corresponding to different S-Docs pages:
* Generate Documents page
* Edit Document page
* Send Email page
* Contact Lookup window
* Attach Files window
* Upload Files tab
* Mass Merge interface
For each section:
1. **The English version** of each field appears on the left
2. **Enter your translation** in the text box on the right
3. **Click "Save"** when you've completed your translations
**Important:** When you save a new language, two new S-Docs templates will be created automatically. These templates contain the saved translation settings and any UI translations you've defined, and should not be edited directly.
{% endstep %}
{% step %}
#### Step 4: Translation Activation
After defining and saving your translations, the S-Docs UI will automatically be available in the translated language for users whose Salesforce language settings match the translation language you created.
{% endstep %}
{% endstepper %}
***
## User Language Settings
The S-Docs UI translation that displays for each user is determined by their Salesforce language settings. To ensure users see the translated interface:
1. Navigate to Setup → Users → select the user
2. Verify the user's **Language** field is set to match one of your defined S-Docs translations
3. The S-Docs UI will automatically display in that language when the user accesses S-Docs
Alternatively, users can update their own language preferences:
1. Click on their profile icon → Settings
2. Navigate to Language & Time Zone
3. Update the **Language** setting
***
## Combining UI and document translations
You can use both UI translations and document translations together for a fully localized experience. When configured properly, S-Docs can provide:
* Translated S-Docs interface (based on user's Salesforce language settings)
* Translated field labels and picklist values (using Translation Workbench)
This provides a complete translation experience—from the user interface through to the final generated document content.
***
## Best Practices
* **Maintain consistency**: Use the same language names across your translation settings
* **Test the experience**: Generate documents using the translated UI to ensure all pages display correctly
* **Update regularly**: If S-Docs releases new features, revisit your custom translations to include any new UI elements
* **Align with Salesforce languages**: Ensure your S-Docs translation language names correspond to languages available in Salesforce
* **Don't edit generated templates**: The two templates created when saving translations are system-generated—editing them directly can cause issues
* **Communicate with users**: Inform employees that they can control which language the S-Docs UI displays in by updating their Salesforce language settings
***
## Troubleshooting
Translations not appearing
* Verify the user's Salesforce language setting matches the language name defined on the S-Docs Translation page
* Ensure you've clicked "Save" on the S-Docs Translation page after defining translations
* Check that the translation templates were created successfully after saving
Partial translations showing
* Review the S-Docs Translation page to ensure all UI sections have been translated
* Some elements may default to English if translations are incomplete
Language mismatch
* Confirm the language name in S-Docs exactly matches Salesforce's language naming conventions
* Language names are case-sensitive and must match precisely
***
Translating the S-Docs user interface ensures that your global workforce can generate professional documents efficiently in their native language, improving productivity and user satisfaction across your organization.
---
# 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/translating-the-s-docs-user-interface-ui.md?ask=
```
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.