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

# Set your brand

> Turn on white label, give the app-building agent your platform's name, and set the design system your apps are built with.

Your brand is what your builders see while they build. It has two parts, the name the agent goes by and the design system your apps follow.

Once white label is on, every app built or edited in your workspace follows your white label settings: your brand and agent names, your design system, your [skills](https://docs.base44.com/developers/white-label/skills-and-mcp.md), and your [system prompt](https://docs.base44.com/developers/white-label/system-prompt.md) if you wrote one. New apps use them from the first build. Existing apps pick them up from their next build turn, including in conversations already under way. The same goes for any change you save later.

> [!WARNING]
>
> You need a workspace owner or admin role, on the [Builder plan](https://docs.base44.com/Account-and-billing/Billing-and-plans.md) or above.

## Turn on white label

When you turn on white label, in the app or with the API, you accept the [White Label Terms](https://docs.base44.com/Community-and-support/white-label-terms).

**To open your white label settings:**

1. Click your workspace name at the bottom left, then click **Settings**.
2. Under **White label**, click **Settings**.

Until white label is set up, the page shows two setup steps:

* **Set up white label in Base44:** Opens a new Base44 chat with the setup prompt filled in. Use **Copy prompt** instead to paste it into your own coding agent. The prompt includes your workspace ID.
* **Create an access token:** Opens [personal access tokens](https://docs.base44.com/Workspaces/Personal-access-tokens.md). The agent asks for this token during setup.

The agent turns white label on and saves your brand name with the [API](#use-the-api). Once it does, the page shows your settings. To turn white label on yourself after it's been set up once, click **Turn on white label** in the **Setup and status** card.

## Name your agent

By default, the agent introduces itself as Base44. Give it your platform's name instead.

**To name your agent:**

1. Open **White label** → **Settings** in your workspace settings.
2. In the **Your brand** card, enter your platform's name in **Brand name**.
3. (Optional) In **Agent name**, enter the name the assistant introduces itself with. Leave it empty and the agent uses your brand name.
4. Click **Save**.

Each name can be up to 48 characters, and your brand name is required while white label is on. Use your own names, not Base44.

## Set your design system

A design system sets the colors, fonts, and component styles your apps use. On Enterprise, your workspace can hold any number of design systems. On other plans, it can hold one. Only one is the default.

> [!NOTE]
>
> **When the default design system applies:**
>
> * **White label is off:** New apps use your default design system automatically.
> * **White label is on:** Apps use it only when **Use design system** is also on. Turn it on after you set your default.

With Base44's prompt, the agent gets your design tokens, such as colors, typography, spacing, radii, and shadows. With [your own prompt](https://docs.base44.com/developers/white-label/system-prompt.md), it also gets your design guidelines and component styling rules. If no default design system is ready, the agent continues without one.

### In the app

**To set your design system in the app:**

1. [Create a design system](https://docs.base44.com/Building-your-app/Design-system.md) from your brand, and wait for it to finish generating.
2. [Set it as your workspace default](https://docs.base44.com/Building-your-app/Design-system.md#setting-a-default-design-system).
3. Open **White label** → **Settings**, and in the **Design system** card, turn on **Use design system**. The switch saves immediately.

The **Design system** card shows your default. To change it, click **Manage design system**.

### With the API

The API calls a design system a brand. Call these endpoints with a personal access token that has **Full access**, created by a workspace owner or admin in the workspace. Workspace API keys aren't accepted.

**To set your design system with the API:**

1. Call [Generate workspace brand](https://docs.base44.com/api-reference/generate-workspace-brand.md) with a `description` of your brand. It returns the new brand's `id` right away and builds it in the background. If you already have a design system, add it with [Create workspace brand](https://docs.base44.com/api-reference/create-workspace-brand.md) instead.
2. Poll [Get workspace brand](https://docs.base44.com/api-reference/get-workspace-brand.md) every few seconds until `status` is `ready`. If it's `failed`, `failure_message` says why.
3. Call [Set default workspace brand](https://docs.base44.com/api-reference/set-default-workspace-brand.md). A workspace's first brand becomes the default on its own.
4. Set `use_default_design_system` to `true` with the [white label settings endpoint](#use-the-api).

## Use the API

You can read and change your white label settings at `/api/workspace/{workspace_id}/white-label` on `https://app.base44.com`. The endpoints are in beta. Use a personal access token with **Full access**, created by a workspace owner or admin in that workspace. A read-only token can read your settings but not change them, and a token limited to selected apps isn't accepted. If your plan includes [workspace API keys](https://docs.base44.com/Enterprise/workspace-secrets.md), you can use a key for the workspace instead. The key acts as the workspace owner, and a read-only key can't change your settings.

| Method | What it does |
| :- | :- |
| `GET` | Returns your settings: `enabled`, `brand_name`, `agent_name`, `agent_prompt`, and `use_default_design_system`. It also returns `controls_visible`, which says whether white label is available to your workspace, and `can_edit_brand` and `can_edit_prompt`, which say whether your plan allows the brand fields and your own prompt. |
| `PATCH` | Changes only the fields you send, and returns your settings after the change. Leave a field out, or send `null`, to keep it as it is. |

**PATCH fields:**

| Field | Type | What it sets |
| :- | :- | :- |
| `enabled` | boolean | Turns white label on or off. Turning it on needs a brand name, either already saved or sent in the same request. Turning it off works on every plan. |
| `brand_name` | string | Your platform's name. It needs at least one letter or number, and can't be `Base44` in any capitalization. Base44 replaces line breaks, tabs, and the characters `< > { } [ ] \` with spaces, and keeps the first 48 characters. |
| `agent_name` | string | The name the agent introduces itself with, with the same rules as `brand_name`. Send an empty string to go back to your brand name. |
| `use_default_design_system` | boolean | Whether apps use your workspace's default design system. |
| `agent_prompt` | string | Your own [system prompt](https://docs.base44.com/developers/white-label/system-prompt.md), up to 60,000 characters. Enterprise only. Send an empty string to go back to Base44's prompt, which works on every plan. |

**To turn on white label and name your agent in one call:**

```bash theme={null}
curl -X PATCH "https://app.base44.com/api/workspace/$BASE44_WL_WORKSPACE_ID/white-label" \
  -H "Authorization: Bearer $BASE44_WL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"enabled": true, "brand_name": "Northlight Studio", "agent_name": "Scout", "use_default_design_system": true}'
```

| Error | What it means |
| :- | :- |
| `400` with `brand_name_required` | You're turning white label on without a brand name. |
| `400` with `invalid_brand_name` or `invalid_agent_name` | The name has no letters or numbers. |
| `400` with `reserved_brand_name` | The name is `Base44`, in any capitalization. |
| `403` with `forbidden` | The token's account isn't an active workspace owner or admin, or the token or key is for a different workspace, is read-only, or is limited to selected apps. |
| `403` with `white_label_plan_required` | The brand fields need the Builder plan or above. |
| `403` with `agent_prompt_plan_required` | Your own prompt needs the Enterprise plan. |
| `404` when turning it on | White label isn't available for your workspace yet. Contact your onboarding contact. |
| `422` | The request body is malformed, or `agent_prompt` is longer than 60,000 characters. |
| `429` | You've sent too many requests. Reads allow 120 a minute and changes allow 30 a minute. Each response reports your remaining budget in `X-RateLimit-Remaining`. |

## Turn off white labeling

**To turn off white label:**

1. Open **White label** → **Settings**.
2. In the **Setup and status** card, click the **More actions** menu, then click **Turn off white label**.
3. Click **Turn off** to confirm.

From their next message, your builders chat with Base44 again, and the agent stops using any prompt you wrote. Your brand, skills, and design system stay saved, so you can turn white label back on anytime with **Turn on white label**. With the API, send `PATCH` with `{"enabled": false}`. Turning off works on every plan.

## See also

* [System prompt](https://docs.base44.com/developers/white-label/system-prompt.md): Change how the agent behaves across your workspace
* [Skills and MCP](https://docs.base44.com/developers/white-label/skills-and-mcp.md): The rules the agent follows and the tools it can call
* [Setup checklist](https://docs.base44.com/developers/white-label/setup-checklist.md): Everything you need to do to get an integration running


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.