Your Interface, Their Language

12-Language Support and Per-Group Language Lock in LC Learn

April 10, 2026 — By Brent Miller

When we launched the first beta of LC Learn earlier this year, the interface was bilingual — English and Spanish. That was enough for our initial testers, but it was never going to be enough for the kind of classrooms we're building for.

As of this week, LC Learn supports twelve interface languages: Dutch, English, French, German, Greek, Italian, Polish, Portuguese, Romanian, Spanish, Swedish, and Turkish. Every menu, button, instruction, feedback message, score banner, and legal document has been translated. And the way students encounter those languages is entirely under the teacher's control.

What "multilingual" actually means here

Most platforms handle language as a global preference: you pick a language in your profile settings, and the whole interface switches. That works for a single user. It does not work for a language teacher who has three groups of students, each studying a different target language.

In LC Learn, the interface language is resolved through a four-step chain:

Group language lock — if the teacher has locked this group to a specific language, that wins. The student sees everything in that language, no exceptions.
Student preference — if the student has chosen a language in their Settings page, that is used next.
Browser language — if the student hasn't set a preference, we read their browser's Accept-Language header and match it to our twelve supported languages.
English — the final fallback.

Teachers always see their own chosen language, completely independent of what their students see. There is no cascade from teacher to student.

Per-group language lock: why it matters

The feature that makes this genuinely useful for language courses is the per-group language lock.

Imagine you teach English and French at a language school in Istanbul. You have three active groups this term:

An intermediate English group — you lock the interface to English. Every student in this group sees all menus, buttons, instructions, and feedback in English, regardless of their personal preference — except the initial privacy agreement, which always appears in the student's own language. Full immersion.
A beginner French group — you leave the lock off at the start of the year, so your Turkish-speaking students can find their way around the platform in Turkish while they build confidence. The course itself is a French–Turkish bilingual course, with Bilingual Support tags placed where a beginner naturally needs a hand, so students see Turkish support text alongside the French content. Later in the year, when the group is ready, you flip the lock to French and the entire interface switches to immersion.
An online CLIL course on AI and Robotics with international reach — students joining from Turkey, Poland, Greece, and Romania. You leave the lock off entirely. Each student sees the interface in their browser's language or can choose one from their Settings page. The course content is in English, but the surrounding interface — buttons, instructions, score feedback — meets each student in their own language, removing a layer of friction that has nothing to do with the subject.

You, the teacher, see your own dashboard in Turkish throughout. The language lock is per-group, not per-teacher — so your choice for one group does not affect any other.

This is a small thing on the surface. In practice, it is the difference between a platform that supports multilingual classrooms and one that merely allows a language setting somewhere in a menu.

The signup problem

One detail we sweated over: what happens when a new student signs up for a language-locked group?

Before a student has accepted the privacy notice and terms of service, they have not yet consented to anything. Showing that consent screen in a language they might not fully understand — because their teacher locked the group to the target language — would be legally and ethically wrong.

So we added a pre-consent bypass. During the signup and privacy-notice flow, the language lock is suspended. The student sees those screens in their browser's language (if it is one of our twelve supported languages) or in English. Once they have read and accepted the privacy notice, the group lock takes effect and the immersion begins.

This means a Polish student joining a French-locked group will see the privacy agreement in Polish, click through, and then immediately see the full LC Learn interface in French. The transition is seamless. The consent is meaningful.

Beyond language courses

The per-group language lock was designed with language immersion in mind, but the broader multilingual support is just as valuable in contexts that have nothing to do with foreign language teaching.

Consider a math teacher in a multilingual school. The class includes students whose first language is Dutch, Turkish, Polish, and Romanian. Without language support, every student sees the interface in English (or whatever the platform default is), regardless of whether they are comfortable reading instructions in that language.

With LC Learn's browser-language detection, each student automatically sees the interface in their own language — no teacher intervention required. The math content itself stays in whatever language the teacher authored it in, but the surrounding interface — "Submit," "Next question," "Your score," "Try again" — appears in the student's native language.

For students who are still building confidence in the language of instruction, that small shift removes a layer of friction that has nothing to do with the subject being taught.

Students choose too

When a group is not language-locked, students have a simple language selector in their Settings page. Twelve languages, listed with their native names and flag emoji, one click to save. The change takes effect immediately.

When a group is locked, the Settings page shows a clear, read-only message: "Your teacher has set the interface language to French. Contact your teacher if you need it changed." No confusion, no hidden override.

This is a deliberate design choice. The teacher's pedagogical decision — "this group works in French" — takes priority over individual preference. But the student always knows what is happening and why.

Bilingual Support tags for low-level learners

Alongside the multilingual interface, we have just added Bilingual Support tags — a way for course authors to embed mother-language scaffolding directly into lesson content. When a teacher sets a Support Language on a course, any text marked with a Bilingual Support tag is rendered distinctively in that language, sitting alongside the target-language material.

The teacher decides where the help belongs — a tricky instruction, an unfamiliar idiom, a cultural note, the gloss of a key word. Beginners get a hand exactly where they need one, without the page turning into a translation crutch. The pattern works especially well in beginner language courses, where confidence in the target language is still being built.

Twelve languages, fully translated

Each of the twelve languages covers the full interface:

All student-facing pages — assignments, quizzes, scores, feedback, settings
All teacher-facing pages — dashboard, group management, assignment settings, monitoring
The privacy notice and terms of service
Help documentation (five guides)
System messages, error states, and procedural text

The twelve languages in the current release are:

Deutsch (German)
English
Español (Spanish)
Français (French)

Italiano (Italian)
Nederlands (Dutch)
Polski (Polish)
Português (Portuguese)

Român˘a (Romanian)
Svenska (Swedish)
Türkçe (Turkish)
Ελληνικα (Greek)

More languages are on the roadmap, including non-Latin scripts. The framework that supports the current set was built with that expansion in mind, so adding a language is a defined process rather than a fresh engineering problem each time.

Each supported term is translated in the context of where it appears — "Submit" on a quiz page is not always the same word as "Submit" on a registration form. That contextual approach avoids the literal mistranslations that plague machine-translated interfaces. We refine continuously, and feedback from teachers working in their own language is the most valuable input we get.

Try it yourself

If you teach in a multilingual environment — whether that is a language school, a CLIL programme, an international school, or a community education project — we would love your feedback on how this works in practice.

Beta access is open. Join at lessoncommons.com/beta and help us get this right.

Lesson Commons is an educational software platform for teachers and trainers. The editor, delivery platform, and open transfer format (LC.JSON) are in active development. Follow our updates at lessoncommons.com/news.

This article was written with the assistance of Claude (Anthropic). The author defined the purpose, audience, and main ideas, directed the editorial approach, and edited the final text. Claude assisted with structure and drafting.