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

# White-Label Branding

> Replace the default nao branding with your own logos, favicon, and app name

White-label branding lets admins replace the default nao chrome with custom branding. Once configured, your users see your company identity across the chat sidebar, login page, browser tab, and favicon.

<Info>
  White-label branding requires an **Enterprise license** with the `white-label` feature enabled. See the [Enterprise overview](/nao-agent/enterprise/overview) for licensing details.
</Info>

## What you can customize

| Asset | Where it appears |
| - | - |
| **Sidebar logo** | Top-left corner of the chat sidebar |
| **Login page logo** | Sign-up, login, and OAuth consent pages |
| **Favicon** | Browser tab icon |
| **Tab title** | Browser tab text |
| **App name** | Logo alt-text fallback, the name in messaging-channel buttons and cards, and email subjects and copy |
| **Brand color** | Buttons, links, badges, and accents across the app, plus buttons in transactional emails |

## Configuration

1. Sign in as an admin and open **Settings** -> **Appearance**, then find the **Branding** section.
2. Upload your logo files (PNG, JPG, SVG, WebP, GIF, or ICO, up to 512 KB each).
3. Enter your app name and tab title.
4. Set your brand color (see below).
5. Click **Save**. Changes apply immediately for all users.

You can update text fields without re-uploading images and vice versa. To remove an individual asset, click the remove button next to its preview - a "Marked for removal" hint confirms the change before you save.

## Brand color

Pick a custom brand color with the color picker or by entering a hex code. Once set, nao applies it everywhere across the app - buttons, links, badges, and accents - so the product matches your brand.

* A live preview shows how the color renders before you save.
* The color adapts automatically to both light and dark mode, keeping enough contrast so text on top stays readable.
* The brand color is intentionally **not** applied on the login and sign-up pages.

## Messaging channels and emails

White-label branding also reaches beyond the web app, so users on other surfaces see your brand instead of nao's:

* **Messaging channels** - the cards and buttons nao posts to Slack, Microsoft Teams, Telegram, WhatsApp, and Mattermost (the completion card, the `Open in <app name>` button, table and map links, and notification text) use your configured **app name**.
* **Transactional emails** - subjects and copy use your **app name**, buttons use your **brand color**, and the header shows your uploaded logo. The "nao" mention is dropped from the email footer.

<Note>
  Email headers use raster logos (PNG, JPG, WebP, GIF). Vector (SVG) logos are not rendered in the email header.
</Note>

## Supported formats

* **Images**: PNG, JPG, SVG, WebP, GIF, ICO
* **Max size**: 512 KB per asset

## How it works

* Assets are stored in the nao database (consistent with other uploaded content).
* Every read is gated through the `white-label` license feature. If the license lapses or the feature is removed, the default nao branding is restored automatically.
* The `/branding/:kind` endpoint serves assets with a 60-second cache header.

## Visibility

The **Branding** section appears on the **Appearance** page for all non-cloud admins. Deployments without an active Enterprise license see the controls with an inline Enterprise nudge but cannot save changes.

<Card title="Enterprise Overview" icon="building" href="/nao-agent/enterprise/overview">
  License setup, feature list, and how to get a quote
</Card>


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