clerk-orgs

Multi-tenant Clerk Organizations allow B2B users to operate in separate team workspaces. Enable Organizations in Clerk Dashboard, read orgId from auth(), and gate Next.js routes using has({ role: 'org:admin' }) to scope data and navigation per tenant.

Clerk Organization RBAC uses has({ role }) and has({ permission }) checks to enforce access. It supports canonical System Permission slugs like org:sys_* to ensure administrators can securely control access patterns within their specific organization.

Yes, enterprise SSO can be configured per-organization using strategy: 'enterprise_sso' for SAML or OIDC. Access provider metadata by reading from the correct nested fields to enable organization-specific identity provider integration.

Prevent cross-organization data writes by applying Next.js org safety patterns. Implement slug invariants and protect server actions and middleware routes using orgSlug and orgId checks to ensure data operations remain strictly scoped to the active tenant.

Manage member lifecycles by inviting members, assigning roles, and listing or revoking invitations through Clerk APIs or built-in UI components. This requires Organizations to be enabled with a chosen membership mode to handle access correctly.

Yes, you must enable Organizations in the Clerk Dashboard and select a membership mode before implementation. This prerequisite allows the system to properly handle org switching, membership management, and admin-controlled access patterns.