Translating the S-Docs App Menus
Translate the S-Docs user interface for one language, test it with a user, and verify the translated workflow.
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.
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.
Step 2: Try the Fastest Option First
If your language is available, start with the prebuilt template.
Download the matching translation package:
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.
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.
Step 4: Open the S-Docs Translation Page for Custom UI Translation
Use this path when you want to create or edit translations yourself.
Open the App Launcher.
Search for S-Docs Setup.
Open S-Docs Setup.
Scroll to Translate Data/UI.
Click Go To S-Docs Translation Page.
This page lets you manage both UI translations and data translations.
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.
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:
Read the English text on the left.
Enter the translated text on the right.
Continue through the page until each needed label is translated.
Click Save.
Start with the pages your team uses most often.
That usually means Generate Documents, Send Email, and Attach Files first.
When you save a new language, S-Docs creates system translation template records automatically. Do not edit those records directly.
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:
Open Salesforce Setup.
Go to Users.
Open a test user.
Set the user's Language to the target language.
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.
Step 8: Test the Main S-Docs Workflow
Now verify the translated UI in the places users actually work.
Run this quick flow:
Open a record with S-Docs enabled.
Open Generate Documents.
Verify the page labels and buttons are translated.
Generate a document.
Open Send Email.
Verify the email page labels are translated.
Open Attach Files or Contact Lookup if your flow uses them.
Verify those labels are translated too.
If your team uses Mass Merge, test that screen separately.
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.
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.
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
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:
Last updated
Was this helpful?