-
Notifications
You must be signed in to change notification settings - Fork 43
feat: add user org pooling #506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| --- | ||
| page_id: 7e2b8c3a-4f1a-4e2a-9c6b-2d8f7a1b5c3d | ||
| title: Organization User Pools | ||
| sidebar: | ||
| order: 3 | ||
| relatedArticles: | ||
| - 38e9186d-cca5-44a6-86ab-dde9f21167ff | ||
| - 318ccfa9-c7f0-40d9-a2ad-814e4e400af7 | ||
| app_context: | ||
| - m: user | ||
| s: orgs | ||
| - m: settings | ||
| s: environment | ||
| - m: organization | ||
| s: users | ||
| description: Learn how Organization User Pools enable multi-tenant user management by isolating identities within organizations, supporting identity uniqueness, authentication scoping, and secure access control for B2B environments. | ||
| metadata: | ||
| topics: [authenticate] | ||
| sdk: [] | ||
| languages: [] | ||
| audience: [developer, enterprise-admin, security-engineer] | ||
| complexity: advanced | ||
| keywords: [organization user pools, multi-tenant, identity isolation, B2B authentication, user management, organization scoping] | ||
| updated: 2025-07-24 | ||
| featured: false | ||
| deprecated: false | ||
| ai-summary: > | ||
| Comprehensive guide to Organization User Pools - a multi-tenant user management feature that isolates user identities within organizations for secure B2B environments. | ||
| --- | ||
|
|
||
| Organization User Pools is a powerful multi-tenant user management feature that isolates user identities within specific organizations. This feature is essential for B2B applications where you need to maintain separate user pools across different client organizations while allowing the same email addresses or usernames to exist across organizations. | ||
|
|
||
| ## What are Organization User Pools? | ||
|
|
||
| Organization User Pools create isolated user identity spaces within your Kinde environment. Each organization maintains its own pool of user identities, preventing cross-organization identity conflicts and ensuring data isolation. | ||
|
|
||
| ### Key Benefits | ||
|
|
||
| - **Identity Isolation**: Users from different organizations cannot access each other's accounts | ||
| - **Email Reuse**: The same email address can exist across multiple organizations | ||
| - **Secure Multi-tenancy**: Complete data and identity separation between organizations | ||
| - **Scalable B2B**: Support unlimited organizations with isolated user management | ||
| - **Backward Compatibility**: Works with existing authentication flows | ||
|
|
||
| ## Use Cases | ||
|
|
||
| ### B2B SaaS Applications | ||
| - **Multi-tenant platforms** where each client organization has isolated users | ||
| - **Enterprise applications** requiring strict data separation | ||
| - **Partner portals** with organization-specific access | ||
|
|
||
| ### Enterprise Organizations | ||
| - **Internal departments** with separate user management | ||
| - **Subsidiary companies** requiring isolated user pools | ||
| - **Client-specific deployments** with unique user spaces | ||
|
|
||
| ### Example Scenario | ||
|
|
||
| Consider a project management SaaS serving multiple companies: | ||
|
|
||
| ``` | ||
| Company A (org_company_a): | ||
| - [email protected] | ||
| - [email protected] | ||
|
|
||
| Company B (org_company_b): | ||
| - [email protected] (same email, different organization, different password) | ||
| - [email protected] | ||
| ``` | ||
|
|
||
| Without Organization User Pools, the second `[email protected]` would conflict with the first. With Organization User Pools enabled, both can coexist safely. | ||
|
|
||
| ## How to Enable Organization User Pools | ||
|
|
||
| This is disabled by default. This can be enabled by updating the environment settings when the account has no users. | ||
|
|
||
| 1. Visit "Settings > Environment Details" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You may not be done with the doc Daniel, but please note this is not the style we do steps in. Can you update to:
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, I wondered if this feature belongs more under Environment > 'Policies' rather than the top level page? |
||
| 2. Click the "Enable Organization User Pools" toggle | ||
| 3. Click "Save" | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Daniel. I don't think 'user pools' should be treated as a proper noun (capitalised) unless it is referring to some actual piece of tech called 'User Pools' (and is an equivalent of 'Twilio' .
If this just refers the feature name we have given it, please make it lower case throughout the doc and in the UI as well. An exception might be the first instance in the doc, where you might use it like you are explaining a term. E.g. Organization 'user pools' refers to the confinement of users to a specific organization... etc. And from then on you can just use lower case. Hope that makes sense.