Skip to main content

White-label experience

Tenant administrators configure branding under Experience. Presentation is versioned separately from assurance policy so a colour change cannot modify evidence requirements.

Brand controls​

  • product/display name;
  • approved logo or mark;
  • primary/accent colours;
  • welcome and support copy;
  • locale strings;
  • support contact; and
  • completion behavior.

The editor previews contrast and mobile layout. Protected consent, capture integrity and security messages cannot be removed by theming.

Custom domains​

  1. Add the requested verification hostname.
  2. Publish the Assayra-provided DNS ownership proof.
  3. Wait for server verification.
  4. Authorise TLS issuance.
  5. Publish the experience release.
  6. Test application links, camera permissions, callbacks and CSP on the exact hostname.

Do not point traffic before ownership and TLS status are approved. The platform keeps tenant and Control Tower origins separate.

Releases and rollback​

Brand/locale changes produce immutable releases. Publish deliberately and retain the previous release for immediate rollback. Applications reference the experience release active at journey start so audit and support can reconstruct what the applicant saw.

Embedded mode​

When using an iframe/WebView, update your host CSP and permission policy for the exact custom origin. Re-run origin/bridge tests after any hostname change.