What customers can do
The three questions that fill webhook support queues — did you send it, what’s in it, can you resend it — are all answerable in the portal without your involvement.
Mint an access link
Access is link-based. Your backend requests a URL and hands it to the customer, typically behind a “Manage webhooks” button in your product or in an onboarding email:200 OK
The token travels in the URL fragment, which browsers do not send to servers, so it stays out of access logs. Links are cheap to create; mint a fresh one per click rather than storing them.
Revoking access
Sessions expire on their own. To cut access off early, for example when a customer’s staff member leaves or a link leaks, expire everything for that customer at once:Embedding
The portal can run inside your product as an iframe. Embedding is off by default and allow-listed per environment: add your app’s origins under Settings → Portal (up to 20), and the portal will only render inside frames on those origins. Combine an embedded portal with short-lived or read-only links minted per page view.Previewing
From any customer’s page in the dashboard you can open their portal directly in a one-hour preview session. Use it to check your branding and to see exactly what a customer sees before you ship them a link.Continue
Customization
Put your name and theme on the portal.
Event docs
The same catalog, published as public documentation.
Customers & endpoints
Manage the same objects from your backend.