> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Control which experiences get translated

> Turn automatic translation on or off for a specific portal experience.

{/* Why */}

Once you have active languages, every partner-facing experience is translated by default. That is usually what you want, but some portals, like a region-specific experience that should stay in one language, need to opt out. This guide shows how to flip translation on or off for a single experience, so you translate broadly while keeping control exactly where it matters.

## What you'll achieve

A specific portal experience that either participates in your program's translation (arriving in each partner's language) or is deliberately held to a single language, decided independently of every other experience.

## Before you start

<Steps>
  <Step title="Add your languages first">
    Languages must be active before an experience can be translated into them. Set them up under [Languages](https://app.introw.io/settings/languages) (see [Set up portal languages](./set-up-portal-languages)).
  </Step>

  <Step title="Have the experience built">
    You need an experience to configure. Create one in the [Experience builder](https://app.introw.io/templates) first.
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Open the experience">
    Go to the [Experience builder](https://app.introw.io/templates) and open the experience you want to configure.
  </Step>

  <Step title="Open its settings">
    Open the experience's settings dialog from the builder. This is where per-experience behavior, including translation participation, is controlled.
  </Step>

  <Step title="Set the multilingual toggle">
    Use **Enable multilingual for this experience** to decide whether this experience is translated.

    * **What it is** - a per-experience switch that includes or excludes this single experience from your program's automatic translation. When on, the experience is translated into the languages configured in your **Languages** settings; when off, it stays in one language regardless of how many locales are active.
    * **Why it matters** - it lets you keep most portals multilingual while pinning a specific one (for example a single-market or single-language partner experience) to one language, without touching your org-wide language list.
    * **How to set it** - leave it on for partner-facing portals that should follow each partner's language; turn it off only for an experience that must stay single-language. The change saves as you toggle it.
  </Step>
</Steps>

## Verify it worked

Preview the experience in another language. With the toggle on, partner-facing content appears translated; with it off, the experience stays in its single language even for partners whose language differs.

## Related

<CardGroup cols={2}>
  <Card title="Set up portal languages" icon="book-open" href="./set-up-portal-languages">
    Add the languages to translate into.
  </Card>

  <Card title="Build and publish a portal experience" icon="book-open" href="/features/portal/experiences/guides/build-and-publish-a-portal-experience">
    Create the experience first.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full configuration options.
  </Card>
</CardGroup>