Overview
The need for a hierarchical structure within Auth0, such as a parent-child relationship between organizations, has been raised to enable a clearer separation and delegation of roles across different organizational levels. This would allow an organization to have sub-organizations or child organizations (e.g., “Top-organization” and “Child-organization”) that inherit or delegate certain permissions and roles.
Applies To
- Auth0 Organizations feature
- Hierarchical roles and permissions
- Access control for organizational structures
Solution
Currently, Auth0 does not provide native support for a hierarchical organizational structure (parent-child relationship) as part of the Organizations feature. However, feedback on this feature is considered highly valuable, as it can inform Auth0’s product development. A feature request can be submitted for consideration in future releases through the Auth0 Feedback portal: Auth0 Feedback.
An alternative approach is to simulate a hierarchical structure externally by storing an organizational relationship key within the user’s app_metadata and leveraging the Role-Based Access Control (RBAC) feature in Auth0. This enables the implementation of role hierarchies by setting permissions and roles within the application, effectively managing access control based on the organizational relationship. Refer to this documentation for additional guidance: Auth0 RBAC Documentation.