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

# White-Label Setup

> Prepare branding, domains, and operational ownership for partner-managed customer environments.

# White-label programs usually require clear separation between platform concerns and partner-owned presentation concerns.

## Ownership boundaries

* Which login domain the customer sees
* Which support/status endpoints are customer-visible
* Which email sender identity owns notifications
* Which reporting and webhook destinations are partner-managed versus customer-managed
* Which tenant provisioning controls remain partner-only

## White-label launch checklist

<Steps>
  <Step title="Provision branded domain and routing">
    Configure domain mapping and verification for the customer-facing host.
  </Step>

  <Step title="Apply brand profile and outbound identity">
    Align logo, color, and notification sender identity for customer-facing experiences.
  </Step>

  <Step title="Set tenant and key governance">
    Ensure tenant-level API keys, webhook endpoints, and ownership metadata are isolated per customer.
  </Step>

  <Step title="Validate support and incident handoff">
    Define whether first-line support is partner-owned or shared and publish escalation runbook.
  </Step>
</Steps>

## Risk controls

* Do not share webhook destinations across customers.
* Keep per-tenant key rotation schedules.
* Ensure audit logs map operational actions to the correct tenant and operator.
* Validate branding changes in sandbox before production rollout.

<Note>
  Treat white-label enablement as an operational program, not only a visual theme change.
</Note>