What problem does it solve? Building multi-tenant B2B SaaS requires organization switching, role-based access control, member invitations, and enterprise SSO — all of which are error-prone to wire up correctly with Clerk. This Skill provides the canonical patterns, permission slugs, and configuration steps so org features work the first time. ## Core Features & Use Cases - Org-aware routing and authorization: Read orgId/orgSlug from auth(), validate URL slugs against the active org, and gate pages with has({ role }) or has({ permission }) using canonical System Permission slugs. - Member and invitation management: Send, list, and revoke organization invitations via the Backend API with required inviterUserId, or use the built-in <OrganizationProfile /> UI. - Enterprise SSO and verified domains: Configure per-org SAML/OIDC connections, access provider metadata via enterpriseAccounts[i].enterpriseConnection, and understand JIT provisioning. - Use Case: Add an <OrganizationSwitcher /> to a Next.js dashboard, scope all data queries by orgId from the session, and restrict an admin settings page to users with the org:admin role. ## Quick Start Ask the AI to add Clerk organization support with an org switcher and org-scoped dashboard data to your Next.js app.