Set up languages and translations

Choose the languages customers can use in Settings → Languages & translations → Languages. Portal buttons and labels use built-in translations. Your own posts and comments need content translations.

Language settings in a demo portal.

Set the default and additional languages

  1. Choose the portal's Default language.
  2. Select the additional languages you want customers to use.
  3. Save.

See supported languages for the available language codes. Customers can choose an enabled language in the portal. A supported ?lang=xx URL value, a saved language choice and the browser's preferred language can also determine what they see. When content has no usable translation, the source text is shown.

The admin dashboard follows your user language. Admin text is available in English, Dutch, German, French, Spanish and Italian. Other languages use English for admin text that has not been translated yet. Interface translations do not use AI credits. Translating content does not translate text inside uploaded images, attachments or videos.

Translate the labels you created

Your board names, statuses, categories, topics and custom field labels are separate from ProductLift's built-in interface text.

Use the label translation table to enter wording yourself, or Refresh labels to fill missing translations with AI. Manual entry uses no AI credits. An AI label batch costs one credit per language, rather than one per label.

Translate new and existing posts

Enable Auto-translate posts if new posts should be translated into each supported language automatically. This costs one credit per post per target language. Three additional languages therefore cost three credits for a new post.

Use Refresh posts for existing content with missing or outdated translations. Review the estimated count and credits before starting. Refresh everything (stale) also covers labels.

Source edits can make AI translations outdated. ProductLift falls back to source text while an outdated translation needs refreshing. Hand-edited translations are treated separately so you can review them rather than silently replace them. Use the translation review screen to inspect their state.

On an individual post, Retranslate stale refreshes outdated AI versions. Retranslate all can also replace manual translations, so review that choice before confirming.

Translate comments

Enable on-demand comment translation if visitors should be able to translate a comment. The first translation into a language uses one credit. Later readers can use the stored translation without another generation.

Comments used as changelog descriptions also appear outside the thread. Their translations can be generated ahead of time for that changelog content.

Change the default language carefully

When you change the default, existing translated board names and other labels can become the new source labels. The previous language remains available as an additional language. Labels without a translation keep their existing text.

Posts and comments are not rewritten into the new default automatically by this label switch. Review the content and translation state before changing the default of an established portal.

Emails and users identified from your app

Notification emails use the recipient's enabled language preference, with the portal language as a fallback. If you use SSO, you can pass an enabled language code such as fr with the user details.

Knowledge base AI answers are a separate feature. An answer can be generated in the visitor's language; this does not create a translated version of the source article.

When credits run out

New AI translations may pause. Existing usable translations remain available, and untranslated content falls back to its source. Check AI credits, then use the review screen to identify work that still needs refreshing. Manual translation remains an option.