Open the Translation section to work with Omni’s management dashboards. They help you find the next useful action, inspect past work and keep translations consistent as source content evolves.
Translation coverage
Choose a source language, target language and content root to scan a branch of the content tree. Coverage shows where a target variant is complete, needs translation, needs review or contains only unsupported values. Filter the results, open the affected page, or start the appropriate translation workflow from the result.
Use coverage when beginning a new language rollout, checking a launch branch or prioritising outstanding translation work. It reports the saved state, so save source edits before scanning.
Missing Variants
The Missing Variants dashboard finds pages that exist in the default language but have no saved variant in one or more configured target languages. It is a focused starting point for building out a new language: choose a target-language filter, find the page and select Create translation.
Omni opens the standard translation preview with the missing language selected. Review the supported properties, create the translated draft, then compare and refine it through the normal Umbraco editing workflow.
Source Changes
After Omni translates a value, it records the source text it used. The Source Changes dashboard compares that record with the current saved source and target values to find changed, newly added and removed text. It also flags when a target-language editor has independently changed a translated value.
- Filter by source and target language, then review the affected pages and properties.
- Use the suggested action to open a translation preview.
- Keep the preselected changed properties, or refine the selection before retranslation.
- Review the draft and publish through the normal Umbraco workflow.
Glossary
Create glossary rules for product names, brand terms and recurring phrases. Scope a rule to a language pair when appropriate; either protect a term from translation or supply the required target-language wording. Keep rules concise and test a representative translation after changing them.
Glossary rules affect translation behaviour across the site. By default, Translation-section users can manage them; see Permissions if this should be restricted to administrators.
Translation Jobs and audit trail
Translation Jobs is the operational history for Dictionary, page and section jobs. Search or filter by job type, status and language, then open a job to inspect its requester, timestamps, progress, summary counts and property- or page-level results. Use it to monitor active jobs, investigate failures and answer what was translated, by whom and when.
Jobs can continue after an individual value or page fails, so check the result details rather than treating a completed job as a guarantee that every value was translated. Job-history retention is configured under DiploTranslatorOmni settings.