An in-depth look at Multi-Tenancy in a B2B SaaS application and how using Auth0 by Okta and the Auth0 Organizations feature can help you implement it.
Read more…
Brought to you by Peter Fernandez
Any questions about the article? Feel free to let us know! 
Phew that was a long read but an informative one. I’ve been struggling a bit to understand where organizations fit in the Auth0 world, it’s slightly clearer now. I suppose if we were already managing our users/orgs through existing backoffice processes and sales order processes (which tied to our own entitlements system), we’d continue using those. Would it be fair to say that Auth0 orgs is better when you don’t already have a way of grouping or entitling them… or do you think orgs could sit alongside existing enterprise entitlement systems?
Hi @sha256 
Thanks for taking the time to read this and for the question 
B2B SaaS, in general, is quite a complex topic, so I tried to keep this one aspect - namely Multi-Tenancy - as concise as possible; I agree, it is a bit of a read, but hopefully a worthwhile one, and I’m glad to hear you found it informative 
I suppose if we were already managing our users/orgs through existing backoffice processes and sales order processes (which tied to our own entitlements system), we’d continue using those.
Yes, absolutely right Remember that there’s more to building a B2B SaaS application than just the identity piece, and so whatever sort of application you’re building will undoubtedly need resources and workflow that go beyond what Auth0 provides. Whilst Auth0 does a great job of the Identity & Access Management (IAM) aspect - which almost always informs the likes of sales order processing, etc. - something like Auth0, and the Auth0 Organizations feature, doesn’t provide a general-purpose B2B SaaS solution framework.
Would it be fair to say that Auth0 orgs is better when you don’t already have a way of grouping or entitling them… or do you think orgs could sit alongside existing enterprise entitlement systems?
From an IAM perspective, the Auth0 Organizations feature can absolutely sit alongside existing (enterprise) entitlement systems, and if you’re using Auth0 for identity management in a B2B SaaS scenario, it absolutely should I didn’t get the chance to go into much detail in this article, it already being long enough 
, but in a future article I have planned - currently entitled “What’s in a Membership” - I will illustrate more regarding the use of the Auth0 Organizations feature. In another planned article currently entitled “Vendor vs Subscriber Administration - a Delegated Admin story”, I’ll also explore how it can be leveraged to enable the various delegated administration workflows as well.
Auth0 Organizations not only provides additional context when it comes to the identity represented in an ID Token or an Access Token, say, but it’s also used to directly configure the likes of Universal Login and other functionality within the Auth0 platform itself. In fact, the additional context that Auth0 Organizations provides is a key aspect of leveraging the likes of Okta FGA within a B2B SaaS solution, too.
Hope this helps, but feel free to reach out if you’d like any further clarity 