clerk-orgs
Clerk Organizations for B2B SaaS - create multi-tenant apps with org switching, role-based access, verified domains, and enterprise SSO. Use for team workspaces, RBAC, org-based routing, member management.
Security Assessment
About clerk-orgs
The clerk-orgs skill provides a structured approach to implementing multi-tenant organization management in B2B SaaS applications using Clerk. It solves the common challenge of building scalable team-based systems by enabling organization switching, role-based access control (RBAC), and secure authentication flows. By centralizing organization logic, it allows developers to efficiently manage users across multiple workspaces while maintaining strict access boundaries and identity verification.
This skill includes core capabilities such as creating and managing organizations, handling memberships, and enforcing permissions through roles or fine-grained permissions. It supports organization-based routing using identifiers like orgId or orgSlug, integrates invitation workflows for adding members, and enables enterprise-grade features like SSO and verified domains. Developers can also enforce limits such as maximum allowed memberships and configure membership modes to support either strictly B2B applications or hybrid B2C + B2B models.
Typical use cases include building team collaboration platforms, SaaS dashboards with workspace separation, and enterprise tools requiring strict access control. It is particularly suited for developers working on Next.js or React applications who need to implement organization-aware authentication and authorization. The skill targets teams building scalable SaaS products where managing multiple users, roles, and organizations is a core requirement.
FAQ
How do I enable organizations before using this skill?
Organizations must be enabled in the Clerk Dashboard under Organizations settings. This is a required prerequisite before any organization-related APIs, hooks, or components will function.
What membership modes are available and how do they affect my app?
There are two modes: 'Membership required', which enforces organization membership and disables personal accounts, and 'Membership optional', which allows both personal and organization-based accounts for hybrid B2C and B2B use cases.
What environment variables are required for compatibility?
You must configure NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY in your environment for the skill to function properly.
How can I manage roles and permissions within organizations?
Roles and permissions can be managed through the Clerk Dashboard under organization settings or by referencing the roles and permissions documentation provided in the skill.
Are there any limitations or prerequisites I should be aware of?
Yes, organizations must be enabled in the dashboard before use, and the selected membership mode must align with your app’s architecture (B2B-only or hybrid). Additionally, compatibility depends on using supported SDK versions.
Install clerk-orgs
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
clerk/skills