Venvera runs in five languages: English, German, Spanish, Bulgarian and Arabic. The choice is not just cosmetic. It changes the navigation, buttons and settings you click every day, the framework and control text you assess against, the wording of dashboards and reports, and, for Arabic, the reading direction of the whole interface. This page explains how the language is decided, how any one person can override it for themselves, and what happens when a translation is not yet complete.
The five languages
Each language is shown in its own script, so people pick the one they read most comfortably rather than translating a label in their head.
| Language | Shown in the app as | Code | Direction |
|---|---|---|---|
| English | English | en | Left-to-right |
| German | Deutsch | de | Left-to-right |
| Spanish | Español | es | Left-to-right |
| Bulgarian | Български | bg | Left-to-right |
| Arabic | العربية | ar | Right-to-left |
English is the source language. Every other language is measured against it, which matters for how missing translations behave, covered below.
Tenant default vs your personal language
The tenant default (set by an administrator)
The tenant default is the language new users see the first time they sign in, and the language anyone falls back to if they have not chosen one of their own. An administrator sets it once under Settings in the Interface Language card. It applies to the whole organisation and takes effect immediately on the next page render, so there is nothing to restart or redeploy.
Pick the default that matches where most of your team works. A Bulgarian bank sets Bulgarian; a Spanish insurer sets Spanish. People who need a different language do not have to lobby for a change to the whole tenant, because they can override it for themselves.
Your personal language ("My language")
In the same Settings area, the My Language card is available to every user, not just administrators. Choose any of the five languages to override the tenant default for your account alone, or choose Tenant default to inherit whatever the organisation is set to. The change re-renders the interface right away.
Under the hood the rule is simple: your own choice wins, and only when you have not made one does the tenant default apply. Leaving your personal language on "Tenant default" is the same as never setting it, so if the administrator later switches the organisation to another language, you follow along automatically.
| Tenant default | Your "My language" | What you see |
|---|---|---|
| Bulgarian | Tenant default | Bulgarian |
| Bulgarian | German | German |
| Bulgarian | Arabic | Arabic, right-to-left |
| English | Tenant default | English |
Arabic renders right-to-left
When the resolved language is Arabic, Venvera flips the entire interface to right-to-left. The sidebar moves to the right, tables and cards mirror, and text aligns from the right edge. This is applied to the whole page, not patched screen by screen, so dashboards, forms and reports all read naturally in one direction. Switching to or away from Arabic re-lays-out the interface on the spot.
What gets translated, and what falls back to English
Translation reaches well beyond the menus. Three layers are covered:
- The application interface - navigation, buttons, settings, dashboards, table headings, status labels and system messages.
- Framework content - the built-in text for the frameworks you have enabled, such as DORA, the EU AI Act, GDPR, ISO 27001, NIS2, SOC 2 and the others.
- Control text - the descriptions and guidance that sit on individual controls as you assess them.
Reviewing and overriding translations
Venvera's platform administrators maintain a translation console where every translated string can be reviewed and, where needed, overridden. Because English is the source language, it is never edited there; German, Spanish, Bulgarian and Arabic are. An override requested for a particular phrase, for example a house term your regulator uses, replaces the bundled wording for that string across the product. If a translation reads awkwardly for your jurisdiction, this is the mechanism that fixes it.
Security Awareness Training in every language
Training content is translated into all five languages as well, and trainees do not need a Venvera login to benefit. On the training page, when a course is available in more than one language, a language selector appears at the top and the trainee can switch on the spot. Someone who received an assignment in the tenant's default language can flip it to their own before they start, and the slides, questions and answers follow.
Scenario: one bank, three languages
A Bulgarian bank rolls out Venvera. Its administrator, Milena, sets the tenant default under Settings to Bulgarian, because that is what the compliance and risk teams work in day to day. Every colleague who signs in lands in a fully Bulgarian interface without touching a single setting.
The bank has brought in a German-speaking external auditor, Klaus, for its DORA readiness review. Rather than ask Milena to change anything for the whole organisation, Klaus opens the My Language card and sets his personal language to German. From that moment his navigation, the DORA framework text and the control descriptions all render in German, while everyone else stays in Bulgarian. When his engagement ends and his access is removed, nothing about the tenant needs undoing.
A board member, Amina, reads Arabic. She sets her personal language to Arabic, and her dashboards and board reports render right-to-left, mirrored and aligned for comfortable reading, while pulling from exactly the same underlying data as her colleagues. Three people, three languages, one tenant, and no one had to compromise.