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. 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 and the 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.What’s customizable where
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 inside your own product.
Continue
Customer portal
The surface this theme lands on.
Event docs
Slug, publishing, and what the docs site shows.
Quickstart
Set up the flow first, then brand it.