# How to run multiple groups of users on different domains in the same tenant

**URL:** <https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124>\
**Category:** Get Help\
**Tags:** multiple-domains, user-group, login\
**Created:** [July 18, 2022, 12:54pm UTC](https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124 "2022-07-18T12:54:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eriks](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/eriks/32/34923_2.png) [@eriks](https://community.auth0.com/u/eriks)\
**Post date:** [July 18, 2022, 12:54pm UTC](https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124/1 "2022-07-18T12:54:56Z")

</div>

We have the following use case: We have both single users and company users which are grouped together by their company. We handle the grouping on our side in our database.  
Now some companies want our application to run on their custom domain.

Given that we dont run multiple backends or web apps, but the one web app will be accessible via multiple domains:

Is there a best practice for how to achieve this?  
The straight forward way is to add all the different domains to the allowed callback urls of the application. But this would mean that every time we onboard a new group of users on a custom domain, we would need to add this domain to the application’s allowed callback urls. What if there will be a limit in the future?

Another option is to let the company customer run the frontend on their servers and we add a new application to our auth0 tenant. But the problems remain pretty much the same. A lot of manual work required every time a new group of users is onboarded.

Is there a better way to do this?

To conclude: Is there a best practice or even dedicated way to have multiple user groups that each run our application on their custom domain?

---

<div class="post-metadata">

**Author:** ![john.gateley](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/john.gateley/32/10879_2.png) [@john.gateley](https://community.auth0.com/u/john.gateley)\
**Post date:** [July 19, 2022, 1:11pm UTC](https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124/2 "2022-07-19T13:11:10Z")

</div>

Hi @eriks

You might find Auth0’s Organizations helpful here:

> **[Understand How Auth0 Organizations Work](https://auth0.com/docs/manage-users/organizations/organizations-overview)**
>
> Describes how Auth0 Organizations work, use cases, a sample scenario, planning, and limitations.

Or you could do the new application per customer approach, but instead of doing it manually, use the management API to add the application.

John

---

<div class="post-metadata">

**Author:** ![eriks](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/eriks/32/34923_2.png) [@eriks](https://community.auth0.com/u/eriks)\
**Post date:** [July 19, 2022, 3:16pm UTC](https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124/3 "2022-07-19T15:16:57Z")

</div>

Thank you for your answer!

However, as far as I understand, once we have organizations with distinct authentication schemes, we cannot have single users authenticate via email and password any more?  
Also, how would organizations help with running the app on multiple domains?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [November 18, 2024, 10:58pm UTC](https://community.auth0.com/t/how-to-run-multiple-groups-of-users-on-different-domains-in-the-same-tenant/87124/4 "2024-11-18T22:58:35Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
