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

# Branding and Theming

> Put your name, colors, and logo on the customer portal and public event docs, configured per environment.

The portal and the event docs are surfaces your customers see, so they should look like your product. Customization is per environment, spread over three settings pages in the dashboard.

## Settings → Portal

Two settings live here. The app name is the title customers see in the portal; it defaults to "Webhooks", and most teams set it to their product's name. The allowed embed origins (up to 20) control which of your app's origins may [iframe the portal](/docs/send/portal#embedding). With none set, the portal runs standalone only.

## Settings → Theme

The theme is a token system rather than a single accent color: background, foreground, card, primary, secondary, muted, accent, destructive, border, input, and ring, each with a light and a dark value in `#RRGGBB` or `#RRGGBBAA` form. You override only the tokens you care about, and the rest keep their defaults, so most brands need a handful of values.

One theme covers both the [portal](/docs/send/portal) and the [event docs](/docs/send/event-docs), so the two always match. The portal applies your theme before first paint; customers don't see a flash of default styling.

## Settings → Docs

The event docs site has its own identity settings on top of the shared theme: a page title, a logo, and a favicon, along with the URL slug and publish toggle described on the [event docs page](/docs/send/event-docs).

## What's customizable where

| Surface           | Name       | Theme (light + dark) | Logo & favicon | Custom URL            |
| ----------------- | ---------- | -------------------- | -------------- | --------------------- |
| Customer portal   | App name   | Shared theme         | —              | —                     |
| Public event docs | Page title | Shared theme         | Yes            | Slug on the docs host |

The portal itself has no logo upload and no per-environment domain. Its identity comes from the app name and your colors, and the deeper integration path is [embedding it](/docs/send/portal#embedding) inside your own product.

<Tip>
  After changing the theme, open a customer's portal from the dashboard (a one-hour preview session) to see the result exactly as a customer would.
</Tip>

## Continue

<Columns cols={3} className="gap-y-4">
  <Card title="Customer portal" icon="app-window" href="/docs/send/portal" cta="Portal" arrow="true">
    The surface this theme lands on.
  </Card>

  <Card title="Event docs" icon="book-open" href="/docs/send/event-docs" cta="Docs" arrow="true">
    Slug, publishing, and what the docs site shows.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/docs/send/quickstart" cta="Build" arrow="true">
    Set up the flow first, then brand it.
  </Card>
</Columns>