Why translating the course is only half the job: the case for 90-language learner portals

Most multilingual training projects stop at the course. The content gets translated, the SCORM file is exported, and the job is marked as done. Then the learner logs in.

They see an English login screen. An English dashboard. An English reminder email telling them a course is overdue. And, after finishing a course in their own language, an English certificate. The course spoke to them. Everything around it did not.

That gap is now closed in CourseAgent. Academy, the learner portal built into CourseAgent, supports all 90 course languages - so the portal interface, system emails, notifications and certificates can match the language of the course.

Why the portal matters as much as the course

Learners experience training as a journey, not a single file. For most people, that journey looks like this:

1. An invitation or enrolment email arrives.
2. They log in and land on a dashboard.
3. They browse or filter a catalogue.
4. They complete a course.
5. They receive reminders, notifications and a certificate.

Translating step 4 alone leaves four out of five touchpoints in a language the learner may not read comfortably. For compliance training in particular, that is more than a cosmetic problem. If a learner cannot understand a reminder, they miss a deadline. If a manager cannot read a certificate, it is harder to use as evidence.

What switches when a learner chooses a language

When a learner joins an Academy, they pick their preferred language on first login. From there, the experience follows that choice:

• Portal interface - navigation, dashboards, buttons and labels.
• Course catalogue - learners can filter to courses available in their language.
• System emails and notifications - invitations, reminders and updates.
• Certificates - issued in the learner's chosen language.
• Courses - translated versions of the same course, built and maintained from one source.

Right-to-left languages such as Arabic, Hebrew, Persian (Farsi) and Urdu are supported, so learners reading those languages get a layout that reads naturally.

One Academy instead of one portal per country

A common workaround for multilingual learning is to run a separate portal for each region, or to buy language packs and hire translators for email templates. Every policy update then has to be repeated across every instance.

With CourseAgent, one Academy can serve a global workforce. Authors translate a course once, review it, and keep each language connected to the same source. Learners in different countries use the same portal in their own language.

A practical checklist for multilingual learning

If you are reviewing your current setup, ask:

• Does the login and dashboard switch language, or only the course?
• Are reminder and enrolment emails translated automatically?
• Are certificates issued in the learner's language?
• Can learners filter the catalogue to courses in their language?
• Do right-to-left languages display correctly across the portal, not just inside a course?
• When a policy changes, how many separate versions have to be updated?

If the answer to several of these is "no" or "it depends", the course may be translated but the learning experience is not.

What this means for different teams

Corporate L&D teams can serve distributed staff from one Academy without managing regional portals.

Training consultancies can give each client a branded Academy that works in their learners' languages.

Compliance teams can make sure reminders and certificates are as readable as the training itself.

Getting started

Academy is included from the Scale plan. You can explore how translation works on the translation features page, see how the learner portal fits together on the Academy page, or read how one Dynamic SCORM package can carry multiple languages in Scaling global training: 90 languages in one Dynamic SCORM package.

Translating the course is only half the job. Now the rest of the learner journey can speak the same language.