This documentation applies to Omni for Umbraco 17 and 18. Both version lines have the same functionality and configuration. Choose the package version for your Umbraco site.
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.
Content Overview
Start with Content Overview for missing-variant counts, tracked source changes, recent jobs and Dictionary work. Its headline figures link to the relevant dashboard; ready and review counts open the matching Source Changes filter.
Translation coverage
Choose a source language, target language and content root to scan a branch of the content tree. Coverage distinguishes missing variants, pages that need translation or review, pages that appear covered, unsupported-only pages and pages with no safe text. 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.
Coverage checks presence and tracked state, rather than linguistic accuracy or publication readiness. Review the target copy yourself. Changing the scan's languages or scope requires a fresh scan.
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.
Each missing page/language pair is one missing variant. The list excludes recycled pages and only includes pages you can browse. It uses saved variant metadata, rather than inspecting every property for translation completeness. Filter to one target language to select and preview several pages for a paid batch translation job.
Source Changes
After a successful content translation, Omni stores comparison hashes for source and target text units. The Source Changes dashboard compares those baselines with the current saved values to find changed, newly added and removed text. It also flags when a target-language editor has independently changed a translated value. These baselines are not stored copies of the source or target prose.
This is a work queue for previously translated or tracked pages, including candidates from recent successful job history. Use Translation Coverage for a broader audit that includes never-translated pages. Ready to Translate identifies safely reprocessable changes; Needs Review asks for an editor decision. Check more means more candidates remain unscanned, and Ignore hides a row only for the current browser session.
- 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.
Exact culture rules take precedence over neutral-language and global rules for the same term and matching shape. Each preview or job uses a fresh snapshot; all pages in one section job use the same snapshot, so glossary edits affect subsequent jobs rather than changing a running section midway through.
Translation Jobs and audit trail
Translation Jobs is the operational history for Dictionary, page, section and selected-page batch 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.
Amber warnings and Review suggested badges are separate from errors. A completed job may include intentionally skipped properties or retained text that needs inspection. History visibility follows content browse permissions; non-administrators see only their own Dictionary jobs.
Support and maintenance
Open Translation → Support to preview and copy installation versions, AI components and selected settings for a support enquiry. Nothing is submitted automatically. Review the text before sharing it and follow the troubleshooting instructions.
Settings → Translator settings contains licensing, administrator-managed AI profile choices and maintenance controls. Users with Settings-section access can inspect cleanup status and run metadata/history cleanup. Cleanup never edits Umbraco content, but removing unit-state baselines can cause later comparisons to need review. See retention settings.