Publishing a translation is the final step after the translated draft exists. You enable multiple languages, get the translated draft created (in-app or via import), then publish it so it goes live for readers in that language.
- Enable multiple languages
In Knowledge Settings, turn on multiple languages and add each target language. For each one, you can set a default assignee or translation queue so submitted articles route to the right translators.
- Submit the article for translation
From the published master article, use Submit for Translation. Pick the target language, an assignee or queue, and a due date. This creates a draft translation version in that language.
- Translate the draft
The assignee opens the draft translation, often with the primary article shown side by side, and enters the translated title and body. Alternatively, import a translated file from a vendor or generate a first pass with AI Knowledge Translations.
- Review and publish
Once the translated draft is complete and reviewed, publish it. Its publish status becomes Online, and the Published Translation is now served to readers whose language matches.
The master language chosen when Knowledge is enabled. It holds the canonical content and is the fallback shown when no published translation exists for a reader's language.
A Salesforce queue that holds articles awaiting translation in a given language, so a team of translators can claim work instead of receiving direct assignments.
An optional user or queue that submitted translations route to automatically for each language, removing the need to pick an assignee every time.
An option that auto-generates a draft translation for review, speeding the draft stage while a human still verifies and publishes the result.
- Publishing a translation is separate from publishing the master. A live English master does not make its German draft visible until you publish the German version.
- Republishing the master article does not update existing published translations. They stay frozen until you re-translate and republish them.
- If no published translation exists in a reader's language, they see the default-language version, not an error. Plan coverage around that fallback.
- Code or flows that read a knowledge version should filter on both PublishStatus and Language, or they may pick up a draft or the wrong language.