Can we create multiple Universal Login pages for different applications in the same Auth0 tenant?

Get Help
,
1

Hi Auth0 Team :waving_hand:

I’m currently managing multiple applications under a single Auth0 tenant, and I’d like to confirm if it’s possible to create distinct Universal Login pages for each application.

Scenario:

  • App A → Custom branding (logo, theme, etc…)

  • App B → Different styling and login flow logic

  • App C → Minimal design with a simplified login UX

From what I’ve seen, the Universal Login page is global per tenant, which means all apps share the same HTML/CSS and login behavior.
However, I’m looking for a way to differentiate the login UI and logic per application, ideally without creating separate tenants.

Questions:

  1. Can we define multiple Universal Login pages within a single tenant?

  2. If not directly, is there a supported workaround (for example):

    • Conditional logic based on client_id or application.name

    • Branding API or dynamic rendering

    • Different branding per app using the new Auth0 Branding feature

My main goal is to provide a unique branded login experience for each product without duplicating tenants.

Any guidance or best practices for handling this scenario would be really appreciated :folded_hands:

Thanks,
Shoaib Raza

3

Hi @shoaib.raza

Welcome to the Auth0 Community!

Please allow me some time to research this issue and I will be back with information as soon as possible.

Best regards,
Gerald

4

Hi @gerald.czifra,

Thank you for the quick response and for looking into this. I’ll wait for your findings.

Please let me know if you need any additional details or setup context from my side to help with the investigation.

Best regards,
Shoaib Raza

5

Hi @shoaib.raza

Back with an update on your use-case and you are correct to think that logic can be applied depending one the client_id to render different login pages. There are different routes that can be taken to accomplish this, depending on a couple of factors, but one approach would be to edit the Lock configuration to accommodate multiple renderings :

if(config.clientID === 'ApplicationAClientID'){
      var lock = new Auth0Lock(config.clientID, config.auth0Domain, {
      ...
      }
    }else{
      var lock = new Auth0Lock(config.clientID, config.auth0Domain, {
      ...
      }
    }

If you are using a custom domain, you can also use the application.id and application.name in order to render different login pages for the same application, as described in our documentation here : Hosting 2 Login Pages on a Single tenant

Allow me to share some useful documentations that should help you achieve this, depending on what would be more feasible for your use case:

I hope these resources help you achieve your desired flow! Please do not hesitate to reach out to us for any other issues or requests, we’ll be glad to look into it for you!

Have a great one!
Gerald

6

Hi @gerald.czifra,

Thank you so much for the detailed explanation and the helpful resources!

I forgot to mention earlier that I’m currently using the Identity-First Login experience. Because of that, I don’t have access to the custom HTML template, so I’m unable to implement the client_id-based logic or Lock configuration you suggested.

Just wanted to clarify this point in case it changes the possible options or recommendations.

Best regards,
Shoaib Raza