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's Organizations APIs, permission slugs, and session tasks. ## Core Features & Use Cases - Org-aware routing and access control: Read orgId/orgSlug from auth(), enforce slug invariants on dynamic routes, and gate pages with has({ role }) or has({ permission }) using canonical System Permission slugs. - Member and invitation management: Send, list, and revoke invitations via the Backend API with required inviterUserId, or use built-in OrganizationProfile and OrganizationSwitcher components. - Enterprise SSO and verified domains: Configure per-org SAML/OIDC connections, JIT provisioning, and correct enterpriseConnection field access. - 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 to your Next.js app with an org switcher, org-scoped dashboard data, and admin-only settings pages.