|
| 1 | +page_id: 7e2b8c3a-4f1a-4e2a-9c6b-2d8f7a1b5c3d |
| 2 | +title: Organization User Pools |
| 3 | +sidebar: |
| 4 | + order: 3 |
| 5 | +relatedArticles: |
| 6 | + - 38e9186d-cca5-44a6-86ab-dde9f21167ff |
| 7 | + - 318ccfa9-c7f0-40d9-a2ad-814e4e400af7 |
| 8 | +app_context: |
| 9 | + - m: user |
| 10 | + s: orgs |
| 11 | + - m: settings |
| 12 | + s: environment |
| 13 | + - m: organization |
| 14 | + s: users |
| 15 | +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. |
| 16 | +metadata: |
| 17 | + topics: [authenticate] |
| 18 | + sdk: [] |
| 19 | + languages: [] |
| 20 | + audience: [developer, enterprise-admin, security-engineer] |
| 21 | + complexity: advanced |
| 22 | + keywords: [organization user pools, multi-tenant, identity isolation, B2B authentication, user management, organization scoping] |
| 23 | + updated: 2025-07-24 |
| 24 | +featured: false |
| 25 | +deprecated: false |
| 26 | +ai-summary: > |
| 27 | + Comprehensive guide to Organization User Pools - a multi-tenant user management feature that isolates user identities within organizations for secure B2B environments. |
| 28 | +--- |
| 29 | + |
| 30 | +# Organization User Pools |
| 31 | + |
| 32 | +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. |
| 33 | + |
| 34 | +## What are Organization User Pools? |
| 35 | + |
| 36 | +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. |
| 37 | + |
| 38 | +### Key Benefits |
| 39 | + |
| 40 | +- **Identity Isolation**: Users from different organizations cannot access each other's accounts |
| 41 | +- **Email Reuse**: The same email address can exist across multiple organizations |
| 42 | +- **Secure Multi-tenancy**: Complete data and identity separation between organizations |
| 43 | +- **Scalable B2B**: Support unlimited organizations with isolated user management |
| 44 | +- **Backward Compatibility**: Works with existing authentication flows |
| 45 | + |
| 46 | +## Use Cases |
| 47 | + |
| 48 | +### B2B SaaS Applications |
| 49 | +- **Multi-tenant platforms** where each client organization has isolated users |
| 50 | +- **Enterprise applications** requiring strict data separation |
| 51 | +- **Partner portals** with organization-specific access |
| 52 | + |
| 53 | +### Enterprise Organizations |
| 54 | +- **Internal departments** with separate user management |
| 55 | +- **Subsidiary companies** requiring isolated user pools |
| 56 | +- **Client-specific deployments** with unique user spaces |
| 57 | + |
| 58 | +### Example Scenario |
| 59 | + |
| 60 | +Consider a project management SaaS serving multiple companies: |
| 61 | + |
| 62 | +``` |
| 63 | +Company A (org_company_a): |
| 64 | + |
| 65 | + |
| 66 | +
|
| 67 | +Company B (org_company_b): |
| 68 | +- [email protected] (same email, different organization, different password) |
| 69 | + |
| 70 | +``` |
| 71 | + |
| 72 | +Without Organization User Pools, the second `[email protected]` would conflict with the first. With Organization User Pools enabled, both can coexist safely. |
| 73 | + |
| 74 | +## How to Enable Organization User Pools |
| 75 | + |
| 76 | +This is disabled by default. This can be enabled by updating the environment settings when the account has no users. |
| 77 | + |
| 78 | +1. Visit "Settings > Environment Details" |
| 79 | +2. Click the "Enable Organization User Pools" toggle |
| 80 | +3. Click "Save" |
| 81 | + |
0 commit comments