EN
English
Default portal language for global teams and English-first rollout programs.
Back to documentation
Company Admin Global Localization
Run the admin portal in the language your operators actually use.
IgniteIQ now supports localized admin operations and learner-facing course content across English, French, and Arabic, with saved preferences, RTL handling, review-first translation publishing, AI repair checks, and safe learner delivery.
FR
French
French admin copy and locale-aware formatting for Francophone operating teams.
AR
Arabic
Arabic admin copy with right-to-left document direction and Arabic-ready typography.
Saved admin preference
Language and font pack choices are saved to the user profile and restored when the admin signs back in.
RTL-aware shell
Arabic changes the root document direction to RTL so navigation, layout, and reading flow match the selected language.
Typography packs
Admins can choose supported font packs for each locale, including Cairo for Arabic and Latin packs for English/French.
Locale-aware surfaces
Dates, billing displays, tracking screens, certificates, dashboard copy, and offline status messaging use the active locale where supported.
Course content translations
How course translations reach learners
Course content is localized through translated overlays, not duplicate course copies. This preserves grading, progress, certificates, assignments, analytics, and the reviewed English source course.
Keep English as source
The original course remains the source of truth for IDs, grading, certificates, assignments, analytics, and learner progress.
Generate locale drafts
Admins generate French, Arabic, or all supported locales from Step 5. Long-running generation uses background jobs with progress instead of a blocking request.
Review before publish
Generated records open in a dedicated review workspace with side-by-side source and target fields, notes, approve, reject, request changes, and safe bulk approval.
Repair safely
Scan for repair detects malformed HTML, source-looking text, RTL risks, and protected quiz or exam structure issues. Fix issues repairs what the system can safely prove.
Use XLIFF when needed
Export XLIFF for professional translators or translation tools, then import it back as reviewed draft content before approval and publish.
Publish explicit locales
Publish French, Publish Arabic, or Publish all reviewed only after the records are reviewed, current, non-blocked, and safe for learners.
Safety rules
Machine translations are never learner-visible until reviewed and published.
Missing, draft, stale, failed, malformed, or hidden locales fall back to English instead of breaking the learner page.
AI repair can translate wording, but protected IDs, answer correctness, scoring, URLs, filenames, and source hashes remain controlled by the system.
Repair jobs and generation jobs are queued, deduplicated, rate-limited per company, and billed through AI credit usage.
Learners can switch between published course languages without creating duplicate enrollment or progress rows.
Admin QA checklist
How to validate localization before rollout
- 1
Open Company Admin Settings.
- 2
Choose the target portal language.
- 3
Confirm the matching font pack is selected.
- 4
For course content, open Step 5 and generate the target locale.
- 5
Review or import translated records, scan for repair, approve, and publish the locale.
- 6
Ask one native-language reviewer to approve course wording before rolling out broadly.
