> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/affiliate-program/branding/portal-translations.md).

# Portal Translations

If your program recruits partners across borders, language is friction. An affiliate navigating a dashboard in a language they don't read works it less, asks more support questions, and trusts the payout numbers less. Bloop lets you override only the strings you care about, so you can localize what matters without a full translation project.

You'll find this under the affiliate **Branding** tab, in the portal translations area.

### Supported languages

Bloop ships portal text in seven languages. Pick the language you want to edit from the language selector:

| Language   | Code |
| ---------- | ---- |
| English    | `en` |
| German     | `de` |
| Italian    | `it` |
| French     | `fr` |
| Arabic     | `ar` |
| Indonesian | `in` |
| Dutch      | `nl` |

Each language has a full set of default strings. You only need to edit the entries you want to change — anything you leave untouched falls back to Bloop's built-in translation for that language.

### How the editor is organized

Translations are grouped by area of the portal. Select a tab on the left (or the dropdown on smaller screens) to load the strings for that area:

* **Common** — shared labels used across the portal.
* **Login** — the sign-in and account screens.
* **Dashboard** — the affiliate's main overview.
* **Product** — product and link-related screens.
* **Commission** — commission and earnings text.
* **Guide** — the help/guide screen.
* **Payment** — payout and payment text.
* **Settings** — the affiliate's account settings.

### Overriding text

Within a tab, each string shows two fields side by side: the **default text** (read-only, for reference) on the left and your **new text** on the right. Type your replacement into the right-hand field, and that becomes the text affiliates see.

Each override is stored against the store, the language, and the specific string key, so:

* Edits apply only to the language you're editing — switching the language selector loads a separate set of overrides.
* A string you leave blank keeps Bloop's default translation for that language.

### Saving

Changes are tracked as you type and surfaced through the save bar at the top of the page. Save to apply your overrides, or discard to revert to the last saved state. Switching languages mid-edit prompts you to confirm before leaving unsaved changes.

### Related

* [Style your affiliate portal](/affiliate-program/branding/portal-style.md) — colors, logo, and title for the same portal.
* [Portal guide](/affiliate-program/branding/portal-guide.md) — write the help content shown on the portal's guide screen.
* [Getting started with affiliates](/quick-start/getting-started-1.md) — overview and onboarding.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloop.plus/affiliate-program/branding/portal-translations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.