nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Override System Terms with Custom Translation Terms

Override System Terms with Custom Translation Terms lets administrators tailor the wording used in the Vanilla interface and translated community content.

Availability (October 21, 2026): This Custom Translation Terms experience is part of Release 2026.017 and is available on standard Public/Corporate and Enterprise communities. Enterprise LTS follows a separate rollout and has not received this feature yet. Check your community’s release version before following the steps below.

Overview

Custom Translation Terms let administrators define preferred wording for specific system terms and other important language. You can use them even when your community does not use AI Translations; AI Translations is only required for custom terms applied to user-generated content.

Before you begin

These steps apply to communities on Release 2026.017 or a later release that includes this feature. Enterprise LTS customers can use them once the feature reaches their LTS environment.
You need the Settings > Manage permission.

Where to find Custom Translation Terms

Access the Dashboard.
Open Settings > Translation Settings.
Select Custom Translation Terms.

Override a system term

To customize a built-in Vanilla term:

Open Custom Translation Terms.
Enter the system term as it appears in the Vanilla interface.
Choose the target language.
Enter the wording you want Vanilla to use.
Select Override System Term.
Select Save.

How custom terms behave

If you leave a target-language value blank, Vanilla continues to use automatic translation for that term when automatic translation is available.

If you do not provide a custom translation for a language, Vanilla uses the standard translation for that language.

Tips

Add the term exactly as it appears in your community content or the Vanilla interface.
Use overrides for terminology and names rather than full sentences or broad translation preferences.
Start with the terms that matter most to members, then expand the list over time.
Review translated content after saving to confirm that your preferred terms appear as expected.