Languages
Languages
The pages your users and your customers' IT admins see can be shown in 21 languages:
| Code | Language |
|---|---|
en |
English |
da |
Dansk |
de |
Deutsch |
sv |
Svenska |
nb |
Norsk bokmål |
fr |
Français |
fi |
Suomi |
es |
Español |
it |
Italiano |
nl |
Nederlands |
pt |
Português |
pl |
Polski |
ro |
Română |
cs |
Čeština |
hu |
Magyar |
el |
Ελληνικά |
bg |
Български |
hr |
Hrvatski |
sk |
Slovenčina |
tr |
Türkçe |
uk |
Українська |
That covers sign-in, sign-up, two-factor and step-up prompts, password reset, invitations and email confirmation, the OAuth consent screen and organization picker, the device sign-in page a TV's QR code opens (Sign in on TVs and devices), the Admin Portal, the error pages, and the emails those flows send.
The signed-in app, including organization and platform administration, supports the same ten languages. Choose your language in the top-right language menu. The choice is remembered in this browser for a year, independently of the hosted sign-in language and its environment policy. Without a console preference, the existing hosted preference or the browser's first supported language is used, falling back to English. The console's confirmation prompts, validation, dates and numbers follow the selected language. Customer names, credentials, permission identifiers and code examples retain their original values.
Existing deployments that explicitly set CBOX_ID_LOCALES keep that hosted-language
allowlist. Add fi,es,it,nl there to offer the four new hosted languages, or use the full
list en,da,de,sv,nb,fr,fi,es,it,nl. Organization language restrictions still apply.
The additional console catalogues and the four new hosted catalogues were machine-translated, with reviewed core interface terms. Automated checks cover keys, placeholders and plural forms; these checks do not replace native-speaker proofreading of every sentence.
How a visitor's language is chosen
Each sign-in page asks these sources in order. The first one that names a language switched on for the environment wins:
ui_localesfrom your app. OpenID Connect lets the app that sends someone to sign in say which languages it wants, most preferred first, separated by spaces:/oauth/authorize?…&ui_locales=da en. The choice lasts for the whole sign-in, so the MFA prompt and the consent screen after it stay in that language.- The visitor's own pick. The language menu in the footer of every sign-in page
remembers the choice in a cookie for a year. Picking a language there also overrides
ui_localesfor the rest of that sign-in. - The browser's language list (
Accept-Language), in the browser's own order.da-DKcounts as Danish, andnocounts as Norwegian Bokmål. - The environment's default language.
A language that is not on the list above is skipped, and so is a supported language that the environment has switched off. Either way the next source is asked.
There is no per-user language setting. The cookie is what remembers someone's choice, because most people use the menu before they have signed in.
Which language emails are sent in
- Emails a person asks for themselves, such as a sign-in link, a password reset or a sign-up confirmation, use the language of the page they asked from.
- Emails an administrator sends, such as an invitation, a password they set or a reset they triggered, use the environment's default language. The console the administrator works in says nothing about the reader's language. The page the email links to then follows the reader's own browser.
A one-time code (a sign-in step-up, approving a device, linking a sign-in method) goes out in the language of the page the person asked for it from, like a sign-in link.
What every email carries
Every email is sent in the brand of whoever the reader was dealing with — the organization's when the email is about one (an invitation to it, its Admin Portal link, its certificate warning, a sign-in on its own page), otherwise the environment's:
- Name: the product name on the Branding page; without one, on a customer's
environment, the environment's name (what its sign-in page is titled); otherwise the
deployment's
CBOX_ID_BRAND_NAME. - Logo: the logo uploaded on the Branding page, served by this deployment from
the address in
APP_URL. A remote image is never used: in an email that is a read receipt. - Colour: the sign-in theme's primary colour, on the button and the top edge of the card, with text on it that stays readable whatever colour you picked.
- Sender name: the email sender on the Branding page; otherwise the brand's name when
the email is branded; otherwise
MAIL_FROM_NAME. The address is alwaysMAIL_FROM_ADDRESS, which your SPF and DKIM records vouch for.
Every email has a plain-text part as well as the HTML one.
Codes are never in the subject line. It is common, and convenient, to put a code in the subject so it can be read from the notification. It can then also be read by anybody who sees the lock screen, a shared inbox's list or a watch, and every one of these codes is a second factor or a proof that the inbox is yours. The subject says what the code is for; the code is the first thing in the email.
Changing the default and the list
For the whole deployment, set two environment variables. See environment variables.
CBOX_ID_DEFAULT_LOCALE=da
CBOX_ID_LOCALES=da,en,sv,nb
For one environment, set default_locale and enabled_locales in that
environment's settings. These are stored with its sign-in appearance and override the
deployment's values:
{ "default_locale": "de", "enabled_locales": ["de", "en", "fr"] }
The console has no screen for these two settings yet. Write them the same way as other
environment settings, for example from php artisan tinker:
$environment = \Cbox\Id\Organization\Models\Environment::find('…');
$environment->settings = [...$environment->settings, 'default_locale' => 'de', 'enabled_locales' => ['de', 'en', 'fr']];
$environment->save();
The default is always kept inside the list. If you name a default that the list leaves out, the first language in the list becomes the default. If only one language is left on, the language menu is hidden.
For developers: adding or changing text
The text lives in lang/<code>/*.php, one file per group: hosted (the shared page
frame), auth, oauth, portal, mail and errors. English is the source:
- Add or change the key in
lang/en/…. - Run
php artisan i18n:types. This regeneratesresources/js/i18n/keys.ts, so React pages can only ask for keys that exist in English. CI fails if that file is out of date. - Add the same key, with the same
:placeholders, to all other supported languages.LangParityTestfails if any language is missing a key, has an extra key, or changes a placeholder.
In React, use useTranslator() from @/i18n. It gives you t(key, params) for text,
rich(key, { name: <b>…</b> }) when a placeholder is a React element, and
choice(key, count) for locale-specific plurals. A page receives only its own group's text.
Danish terminology
The Danish text (lang/da) is written the way a Danish SaaS product would write it, not
word for word from English. Use these terms, so the same thing has the same name on every
page and in every email:
| English | Danish | Note |
|---|---|---|
| sign in (verb) | log ind | "Log ind", "Log ind med adgangsnøgle", "logge ind" |
| sign-in (noun) | login | "Tilbage til login", "Gennemfør login" |
| sign-in link, magic link | loginlink | One word |
| sign out | log ud | |
| password | adgangskode | Never "password" |
| passkey | adgangsnøgle | As Apple and Google say it |
| access key (AWS) | access key | Kept in English, so it is not confused with a passkey |
| two-factor verification | totrinsbekræftelse | The form Google and Microsoft use in Danish |
| authenticator app | godkendelsesapp | |
| recovery code | gendannelseskode | |
| verify, confirm | bekræft | |
| check (running text) | tjek | "Tjek din indbakke" |
| check (a button that runs a check) | kontroller | "Kontroller DNS", "Kontroller og upload" |
| e-mail, e-mailadresse | "Arbejdsmail" for a work email field | |
| account | konto | |
| organization | organisation | |
| workspace | arbejdsområde | Never "workspace" |
| environment | miljø | |
| identity provider | identitetsudbyder | |
| single sign-on, SSO | single sign-on, SSO | Kept in English |
| directory sync | katalogsynkronisering | |
| directory | katalog | |
| log streams | logstreaming | The feature; the targets are "destinationer" |
| audit log | revisionslog | Never "audit-log" |
| tamper-evident | der ikke kan ændres ubemærket | |
| API key | API-nøgle | |
| token, bearer token | token, bearer-token | "et token", "tokenet" |
| app (the one being authorized) | app | "applikation" only where the identity provider's own screen says application |
| authorize (consent) | giv adgang | Permission lines are verbs after "Dette giver … lov til at": "Se dit navn" |
| Cancel | Annuller | |
| Optional | Valgfrit | "(valgfri)" after a common-gender noun, as in "Signeringsnøgle (valgfri)" |
Address and tone. Always "du". In the Admin Portal and the mails to a customer's IT contact, the reader is "du" and the organization's things are "jeres" ("jeres identitetsudbyder"). On the sign-in pages the person's employer is "din organisation".
Protocol words and identity provider labels stay as they are. "Entity ID", "ACS URL", "Client secret", "Single sign-on URL", "Trust policy" and every button or field name in an identity provider's own admin screens are written exactly as that screen shows them. Only the sentences around them are translated.
Writing conventions.
- Sentence case in headings and on buttons: "Sæt jeres organisation op", "Opret arbejdsområde".
- Imperatives without an accent: "Eksporter", "Filtrer", "Kontroller".
- No comma before a restrictive subclause ("den enhed der venter", "en URL der starter med https://"). A comma after a subclause that opens a sentence is kept ("Hvis du ikke har bedt om det, kan du …"), as is the comma between two main clauses ("Vent lidt, og prøv igen").
- Quotation marks are “ ”, never « » or » «. The dash between clauses is a spaced en dash ( – ).
- "én" with an accent when it means the number one ("kan kun bruges én gang").
- Plurals use both forms: "om :count sekund|om :count sekunder", "om :count dag|om :count dage".
- A date in running text takes "den": "udløber den :date".
Related
- Admin Portal — the hosted pages an IT admin opens in their own language.
- For your customers' IT admins — what those IT admins read.
- Enterprise SSO and Social login — the sign-in pages these languages apply to.
Translation sources and review
The additional European catalogs use local TranslateGemma output, with reviewed authentication messages and integer plural forms. Framework validation messages also use Laravel-Lang/lang (MIT; see resources/licenses/laravel-lang.md). Portuguese follows Portugal. These additions are machine-assisted and still need native-speaker review. Catalog parity verifies coverage and placeholders, not linguistic accuracy.
Polish, Romanian, Czech, Croatian, Slovak and Ukrainian carry three plural forms in Laravel order: singular, few, remaining counts. React follows the same order for integer UI counters. Test 0, 1, 2, 5, 11, 21 and 22 when changing counted messages.