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

# Branding

> Your name and logo on your console — and the one name that is not yours to change.

## Your console can carry your identity <Badge color="green" size="sm">LIVE</Badge>

Open **Manage profile** (`/profile`). A **Custom product name** field and a
**Console logo** upload sit there, and saving either changes the name and mark
in the **top-left of your console** on your next page load.

<Warning>
  **Scope, precisely:** this dresses **your operator console** (`/admin` and
  everything under it) and **nothing else**. Your customers' console, the master
  console, and the NeoChamber website are untouched — one datacenter putting its
  mark on its own console must never repaint another's.
</Warning>

### Custom product name

Up to **64 characters** — what you call the console you sell. This is not the
same thing as the display name on your own account, which is a card further down
the same page.

### Console logo

| Requirement | Value           |
| ----------- | --------------- |
| Formats     | PNG, JPEG, WebP |
| Max size    | 96 KB           |
| SVG         | Refused         |

The file's **actual bytes** decide what it is — never its name, never what the
browser declares — so a renamed file is refused rather than trusted.

**SVG is refused deliberately**: an SVG is a document that can carry script, and
your logo is served back from your console's own origin. Export a PNG at 2×
instead.

### Nothing is invented for you

Clear the custom product name and the console falls back to your datacenter's
name, then to the platform's. Remove the logo and the platform mark returns.

### Yours alone

The bytes are served behind your session and scoped to your operator. Another
operator asking for them gets the same answer as for a logo that does not exist.

## The name your customers see is a different setting

Your custom product name dresses **your** console. The **platform brand** is
what *their* console and every page title says.

It is **data, not code**, so a rename takes effect everywhere immediately — but
it is **one row for the whole deployment**. The separate **Branding** card lives
on `/admin/tenants`, not your profile, and renders only for the deployment's
super admin. The API answers an operator account a plain `403`, because a rename
by one operator would rebrand every other operator's customers.

<CardGroup cols={2}>
  <Card title="Managed deployment" icon="cloud">
    Tell NeoChamber the name you want. We set it, and you see it on your next
    page load.
  </Card>

  <Card title="Sovereign / dedicated" icon="building-lock">
    The master console runs inside your own deployment — whoever holds its
    super-admin account sets the name from that same card.
  </Card>
</CardGroup>

<Note>
  **Per-operator branding of your *customers'* console** — your name and mark
  where they sign in, rather than only where you work — is **SOON**. Until that
  row is per-operator, one deployment carries one customer-facing name. That is
  the honest limit, not a setting we have hidden from you.
</Note>