How to configure white-label branding and domains

Documentation
, , , ,
1

How to configure white-label branding and domains

This guide explains white-label setup across branding, custom hostnames, and domain mapping workflows for customer-facing deployments.

Required access: Plan with white-label features enabled.

When to use white-label setup

Use this when delivering client-facing experiences that must reflect custom brand identity and domain ownership.

Prerequisites

Before setup:

  1. Confirm your license includes white-label features.
  2. Confirm domain DNS access is available.
  3. Confirm required client branding assets are ready.
  4. Confirm who owns final domain validation approvals.

How to configure white-label and domains

  1. Open white-label section in dashboard.
  2. Configure brand-level settings and save.
  3. Open CNAME/domain management pages.
  4. Add requested hostname/domain entries.
  5. Apply DNS records at your DNS provider.
  6. Return to dashboard and verify domain validation status.
  7. Test final branded endpoint from a clean browser session.

Verification checklist

Confirm:

  • White-label preset/settings are saved
  • Domain/CNAME validation is successful
  • Branded endpoint resolves over HTTPS
  • Branding appears correctly across key pages

Troubleshooting

If validation fails:

  1. Recheck DNS record value and TTL propagation.
  2. Confirm there are no conflicting DNS records.
  3. Retry validation after propagation window.
  4. Escalate with hostname, DNS screenshots, and timestamp if still failing.

Related guides

  • How to manage connected websites
  • How to use support tickets

Exact route paths

  • /dashboard/whitelabel
  • /dashboard/whitelabel/presets
  • /dashboard/domains
  • /dashboard/cname
  • /dashboard/licenses/[license_key]/whitelabel
  • /dashboard/cname/[license_key]

Expected UI state after each step

  • Step 1: White-label options are visible for eligible licenses.
  • Step 2: Preset/branding settings save successfully.
  • Step 3: Domain/CNAME entries appear with validation status.
  • Step 4: Branded endpoint resolves correctly after DNS propagation.

Screenshot map (step-level)

  1. White-label setup context

  2. Domain validation workflow

Operational objective

Complete the “How to configure white-label branding and domains” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard/whitelabel
  • /dashboard/whitelabel/presets
  • /dashboard/domains
  • /dashboard/cname
  • /dashboard/licenses/[license_key]/whitelabel
  • /dashboard/cname/[license_key]

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: White-label setup context
  • Step 2: Domain validation workflow
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Implementation Team owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Advanced
  • Estimated completion time: 30-60 minutes
  • Owner: Implementation Team
  • Last reviewed: 2026-03-18