Skip to main content
In the Single (IdP) Organizations scenario, every organization that uses the Auth0 Organizations feature uses exactly one Auth0 connection. This feature allows each application to select the appropriate organization defined on the Auth0 Tenant, which will either authenticate user credentials directly or forward the authentication request to the appropriate IdP to handle. In this scenario, we’ll continue to use the Travel0 Corporate Booking example. In this example, the corporate booking application equates to your application and Travel0 corresponds to your company.
Architecture Scenarios - Multitenancy - Diagram - Isolated users, Shared Apps, Orgs A&B
The Auth0 Organizations feature currently supports applications that use the SAML, Open ID Connect protocols and/or the OAuth 2 framework. Applications that require WS-Fed are not supported.
Regardless of how credentials are processed—whether user credentials are stored in a database connection (like with Hoekstra & Associates) or are validated via an enterprise connection (like with MetaHexa Bank) or a social connection—your application behaves the same way. Leveraging the Organizations feature allows you to configure and control the experience.

​
Learn more

Single Identity Provider: Provisioning

Learn about provisioning Organizations for multi-tenant architectures.

Single Identity Provider: Authentication

Learn about authentication users through Organizations for multi-tenant architectures.

Single Identity Provider: Branding

Learn about customizing branding for Organizations in multi-tenant architectures.

Single Identity Provider: Authorization

Learn about authorizing users for Organizations in multi-tenant architectures.

Single Identity Provider: Profile Management

Learn about user profile management for Organizations in multi-tenant architectures.

Single Identity Provider: Logout

Learn about logging users out for Organizations in multi-tenant architectures.