clerk-orgs

Implement Clerk multi-tenant organizations with org-scoped access and RBAC.

Updated May 30, 2026
One-click install
npx skills add https://github.com/Athone88/Anima --skill clerk-orgs-athone88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-orgs
Source: https://github.com/Athone88/Anima/tree/main/.agents/skills/clerk-orgs
Command: npx skills add https://github.com/Athone88/Anima --skill clerk-orgs-athone88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clerk organizations turn a single auth app into a multi-tenant B2B workspace where users can switch orgs and access only the data they’re authorized to see.

Core Features & Use Cases

  • Organization workspace setup: Enable Organizations, create orgs, and route users through org selection based on membership mode.
  • Org-scoped authorization: Gate pages and APIs with roles and canonical System Permissions using has() and orgId/orgSlug checks.
  • Member management & invitations: Manage roles per org and invite new members with the required inviterUserId flow.
  • Enterprise SSO & per-org strategy: Configure SAML/OIDC for each organization and use the enterprise_sso strategy for custom sign-in flows.

Quick Start

Enable Organizations in your Clerk Dashboard with the correct membership mode, then add an OrganizationSwitcher and scope your dashboard data by orgId from auth().

Frequently Asked Questions about clerk-orgs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement B2B multi-tenant organizations in a Clerk-authenticated SaaS?

B2B multi-tenant organizations in Clerk are implemented by enabling Organizations, creating workspaces, and routing users through org selection based on membership mode to isolate data per tenant. You use the OrganizationSwitcher and scope dashboard data by orgId from auth().

How do I enforce org-scoped RBAC permissions for specific routes using Clerk?

Org-scoped RBAC permissions are enforced by gating pages and APIs with roles and canonical System Permissions using the has() function alongside orgId and orgSlug checks. This ensures users only access authorized data within their active organization.

What is the required flow for inviting new members to a Clerk organization?

Inviting new members to a Clerk organization requires using the required inviterUserId flow to manage roles per org. This process ensures that only authorized users can send invitations and assign specific roles within the organization workspace.

Can I configure Enterprise SSO with SAML or OIDC for each organization in Clerk?

Yes, you can configure SAML or OIDC Enterprise SSO for each organization in Clerk by using the enterprise_sso strategy for custom sign-in flows. Correct provider access is verified via the enterpriseConnection property to authenticate users per-org.

Do I need specific Clerk SDK keys to set up organization workspaces?

Yes, setting up Clerk organization workspaces requires Clerk SDK publishable and secret keys to authenticate requests. You also need to enable Organizations in your Clerk Dashboard with the correct membership mode before routing users.

What guardrails exist for maintaining orgSlug invariants during organization switching?

Guardrails for orgSlug invariants ensure the organization slug remains stable and correctly formatted during organization switching and creation. These checks prevent routing errors and maintain consistent org-scoped authorization when users navigate between workspaces.