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

# Branding

Put your logo and favicon on a Portal, and serve it from your own domain.

The **Branding** page holds two cards: **Logo settings**, for the marks a Portal wears, and **Custom domain**, for the address visitors reach it at.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FHJZjksoRWV56btqYaDWL%2Fimage.png?alt=media&#x26;token=eb1da82f-feba-4ea2-9af8-d204f09e1263" alt=""><figcaption><p>The <strong>Logo settings</strong> card: a logo for the light theme, one for the dark, and the favicon.</p></figcaption></figure>

## Company logo

Add a logo for the **Light theme** and one for the **Dark theme**. The Portal shows whichever suits the theme it is running in, so supplying both is worth the minute it takes — a dark logo on a dark header disappears.

Accepts **HEIC, JPEG, PNG or WEBP**, up to **5MB**. A PNG with a transparent background is usually the safe choice.

## Favicon

The small icon in the browser tab. **Recommended 64 × 64px, ICO file.**

It is easy to skip and oddly conspicuous when missing — a Portal with a default favicon looks unfinished in a row of open tabs.

## Custom domain

A Portal is reachable at `portals.scaleflex.com` by default. A custom domain lets visitors arrive at an address of yours instead — `brand.example.com`, say. Set it under **Domain** on this page.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FveoD9XNxVoJuORv7a09O%2Fimage.png?alt=media&#x26;token=b4d50d30-ca3e-4e20-a960-a0d7b86e7d91" alt=""><figcaption><p>The <strong>Custom domain</strong> card, where a domain is requested and selected.</p></figcaption></figure>

### Request a domain

1. Select **Request new**.
2. Enter the domain, without `https://` — for example `brand.example.com`.
3. Submit it. You'll see **Custom domain request submitted**.

The request then goes to Scaleflex to configure. Until that is done it shows as **Pending**, with the note *Awaiting Scaleflex Team Member configuration*.

### What the states mean

| State        | Means                                          |
| ------------ | ---------------------------------------------- |
| **Pending**  | Submitted, waiting for Scaleflex to set it up. |
| **Ready**    | Configured and usable.                         |
| **Rejected** | Not set up.                                    |

Once a domain is **Ready**, select it for the Portal and visitors can reach it there.

### Each domain can open its own Portal

If you run several Portals for different audiences, each custom domain can land on a different one. That is set per domain rather than per project — see [Default portal](https://docs.scaleflex.com/portals/all-portals/settings/default-portal.md).

{% hint style="info" %}
A custom domain with no default Portal of its own sends visitors to the Portal list on `portals.scaleflex.com`, not to your project's default. If a domain should always open one Portal, give that domain its own default.
{% endhint %}
