Skip to main content

Multiple Custom Domains with Branding (Auth Studio)

Overview

From the Custom Domains section in Auth Studio, administrators can:

  • Configure multiple custom domains in the Admin Console
  • Map each domain independently to a V2 or V3 Auth Studio template
  • Control branding and experience per domain without affecting others

This lets you run different brands, regions, or experiences on separate domains while managing them centrally in the Admin Console.

Use cases

Multi-brand identity experiences

  • Use separate custom domains for different brands (e.g., login.brand-a.com and account.brand-b.com) while managing them from a single Admin Console.
  • Map one domain to the V2 Auth Studio template and another to the V3 Auth Studio template to deliver brand-specific login, registration, and MFA experiences.

Gradual migration from V2 to V3

  • Move from V2 to V3 template incrementally, domain by domain, instead of switching all at once.
  • Keep critical or high-traffic domains on V2 while testing and optimizing V3 on selected domains, ensuring a smooth transition with minimal risk.

Region- or audience-specific journeys

  • Configure different custom domains for regions or customer segments (e.g., eu.example.com, us.example.com, partners.example.com).
  • Map each domain to the template version (V2 or V3) and branding that fits that audience, keeping configurations isolated and independently manageable.

A/B testing authentication experiences

  • Run A/B tests by assigning different domains to V2 and V3 Auth Studio templates.
  • Compare completion rates, drop-off points, and user feedback between templates before fully rolling out the new experience.

Independent branding and content per domain

  • Customize logos, colors, and content for each domain without affecting others.
  • Maintain strict brand guidelines for enterprise customers on one domain while experimenting with new designs or messaging on another.

Single account, multiple products

  • Host authentication for multiple products under one account, each with its own domain and Auth Studio template.
  • Ensure each product has a tailored login and registration journey, even when products are at different lifecycle stages (legacy vs. new).

Where to configure it

You can manage multiple custom domains in the Admin Console under: Branding → Custom Domains

In this section, you can:

  1. Add multiple custom domains
  2. Map each domain to:
    • A V2 template, or
    • A V3 template
  3. Configure branding (Style Name) and content per domain/template combination

How it works

1. Create an Auth Studio template

To create an Auth Studio template, go to Auth Studio in the Admin Console

For instructions, see Create a template

2. Add multiple custom domains

From the Custom Domains section, you can:

  • Register multiple domains, for example:
    • abc.com
    • xyz.com
    • login.example.com
  • Complete any required DNS or verification steps prompted by the Admin Console.

Each domain becomes an independent entry you can configure and manage.

3. Map domains to V2 or V3 templates (per domain)

Map each custom domain independently to an Auth Studio template:

  • Example setup:
    • abc.com → mapped to a V2 Auth Studio template
    • xyz.com → mapped to a V3 Auth Studio template

Mapping is per domain, meaning:

  • Changing abc.com from V2 to V3 does not affect xyz.com
  • You can run V2 and V3 experiences simultaneously across domains.

4. Default flow for V2 and V3

For each domain, the user journey follows the default flow of the selected template version:

  • If a domain is mapped to V2:

    • Users see the V2 default flow: layout, steps, and behavior specific to V2

  • If a domain is mapped to V3:

    • Users see the V3 default flow: updated layout, components, and interactions defined by V3

These defaults apply automatically once you map the domain; customize branding and content as needed.

Best practices

Plan domain–template mapping strategically

  • Decide which domains stay on V2 and which move to V3, based on traffic, business criticality, and audience.
  • Start with lower-risk or new domains on V3, and keep mission-critical domains on V2 until you validate the new experience.

Use separate domains for distinct experiences

  • Assign different custom domains for brands, regions, or customer types instead of overloading a single domain.
  • Keep each domain’s mapping and branding focused on a clear use case (e.g., consumer vs. partner vs. internal).

Avoid frequent template switching on the same domain

  • Minimize switching a domain back and forth between V2 and V3 to prevent inconsistent user experiences.
  • Schedule domain mapping changes during low-traffic windows and communicate them to stakeholders.

Keep branding consistent within each domain

  • Ensure logo, colors, and messaging for a domain match the external site or product linking to it.
  • Review Auth Studio after branding changes to confirm login, registration, and MFA screens align with the brand.

Test the full flow per domain before go-live

  • For every custom domain, verify the end-to-end flow (registration, login, password reset, MFA, etc.) in the mapped template version (V2 or V3).
  • Validate edge cases like expired sessions, error states, and redirects to ensure consistent behavior.