# How do I handle "organizations" in a hirearchy

**URL:** <https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811>\
**Category:** Get Help\
**Created:** [June 8, 2022, 1:39pm UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811 "2022-06-08T13:39:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgleason](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jgleason/32/25904_2.png) [@jgleason](https://community.auth0.com/u/jgleason)\
**Post date:** [June 8, 2022, 1:39pm UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811/1 "2022-06-08T13:39:05Z")

</div>

We are a conglomeration of companies and we need to do something like this…

> Brand 1  
> -Accounting  
> -Maintence  
> -Etc  
> Brand 2  
> -Accounting  
> -Maintence  
> -Etc

All of the sub orgs have roles with different permissions. I am not sure how to handle this as there doesn’t seem to be sub orgs. Is there a good way to handle this sort of hierarchical orgs or is this something I have to manage outside of Auth0?

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [June 10, 2022, 12:41am UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811/2 "2022-06-10T00:41:10Z")

</div>

Hey there @jgleason!

Unfortunately, any sort of nested org hierarchy is not supported - I definitely think this is worth a [feedback](https://community.auth0.com/c/feedback/95) post though. Our product teams monitor these and gauge based on community member engagement.

I believe I have seen this accomplished (within Auth0 at least) by breaking out each Brand in this case as its own tenant and going it about it that way.

We always appreciate the feedback 🙂

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [June 25, 2022, 12:41am UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811/3 "2022-06-25T00:41:40Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [November 17, 2022, 8:45pm UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811/4 "2022-11-17T20:45:16Z")

</div>



---

<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:** [August 11, 2025, 11:38am UTC](https://community.auth0.com/t/how-do-i-handle-organizations-in-a-hirearchy/84811/5 "2025-08-11T11:38:11Z")

</div>

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