Hirearchial Organizations

Feature:

I would like to have hierarchical organizations structure

Description:

I would like the ability to create a hirearchial brand structure similar to what is described here (How do I handle "organizations" in a hirearchy)

Use-case:

It would allow finer grain control over access.

Thanks for adding this @jgleason! I imagine it could be a popular one :+1:

I would love to get an understanding of how people are handling this currently. Specifically, we’ll have hundreds or thousands of customers, each with their own company divisions. Creating a new Auth0 tenant for each of these companies (and an Auth0 organization for each division within the company) does not seem tenable. They’ll all be accessing the same application and set of APIs.

We ended up using rules attached to a cloud function that talked to SQL. We used the rule to inject the response into a custom claim.

1 Like

Roles were managed in the db at that point not aith0

2 Likes

Thanks for sharing that @jgleason !

Thanks @jgleason. Using the example in the post you linked to, are you saying you used a role to represent Brand 1-Accounting and another role to represent Brand 1-Maintenance?

I was trying to use organization because I wanted the user to have different permissions on the same thing. The problem is I can’t switch orgs without completely logging back in since the Auth0 UI stuff doesn’t seem to support it.

Also these are hierarchical so I want to be able to set the permission at the highest level and inherit the lower level permissions. So if I am part of Org A and I am granted a permission (user:write) I am also granted that permissions in the Organization B because it is a child of A.