Setting your language

boveDAM is built for bilingual teams and their clients. You can choose between English (en-US) and Mexican Spanish (es-MX) at any time — your preference follows you across every portal you visit, stored in a browser cookie so it persists between sessions.

Where to set your language

There are two ways to set your preferred language.

From the portal header: Every client-facing portal displays a language switcher in the top navigation bar. Clicking it reveals a small dropdown with the available locales — select the one you want and the page re-renders immediately. No full reload required.

From your account settings: If you have a boveDAM account (as an editor, owner, or invited viewer), navigate to Settings → Account → Language preference and select your preferred locale. This setting is applied every time you sign in, on any device.

Both methods write the same underlying preference. If you set your language from the portal header while signed out, the preference is stored as a browser cookie rather than in your account profile. If you later sign in, your account setting takes precedence over the cookie.

What your preference changes

When you set a language, boveDAM renders the following in your chosen locale:

• All portal UI strings — module headings, navigation labels, action buttons, empty states, and system messages
• The portal's top navigation tabs, such as "Logos," "Colors," and "Typography"
• Date and number formatting conventions appropriate to your locale
• Any editor-authored portal description or welcome text, if the editor entered it in your locale

Your language preference applies across all portals you visit on boveDAM, not just the portal where you made the change. If you're reviewing five different client portals in the same session, you'll see the same language throughout all of them.

What your preference does not change

Your language preference controls the portal shell — it does not translate asset content. Specifically:

• Asset filenames are shown exactly as uploaded. A file named Logo_Principal_Azul.svg will always appear with that name, regardless of your language setting.
• Asset metadata — descriptions, tags, alt text, and notes — are displayed in the locale the editor used when entering them. There is no automatic translation.
• Color tokens, typography labels, and module-level names entered by the editor appear as entered.

If your team manages bilingual asset metadata, see Per-portal default locale for how to configure portals for specific audiences, and What renders in which language for the full language resolution order.

Clearing your preference

To return to the portal or workspace default locale, reset your preference using one of these methods:

• Signed-in users: Go to Settings → Account → Language preference and select "Use portal default."
• Guest visitors (cookie-based): Clear the bovedam_locale cookie in your browser's developer tools or privacy settings. On your next visit, boveDAM will fall back to the portal's configured default locale, then the workspace default if no portal locale is set.