René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the Clerk Organizations feature, and what can I build with it?","acceptedAnswer":{"@type":"Answer","text":"
Clerk Organizations let you build authentication, user management, and billing into your B2B SaaS applications without needing to manage complex backend logic or glue code. You can build B2B apps that support teams or company accounts with full organization-level features like multi-tenancy, roles, permissions, and billing. The best part? Clerk lets you support both personal and organization accounts in the same app, so you can offer solo and team plans or workspaces side by side. We provide prebuilt components like <CreateOrganization />, <OrganizationProfile />, <OrganizationList />, and <OrganizationSwitcher /> that you can easily drop into your code to allow users and admins switch between their personal and organization account(s), manage their org’s profile, admin settings, invitations, and even existing members. If you have custom needs that require more control, you can use our APIs to tailor all Organization flows to your specific use case. See custom flows for more information.
"}},{"@type":"Question","name":"Why use Clerk Organizations for B2B SaaS apps?","acceptedAnswer":{"@type":"Answer","text":"
We’ve designed Clerk Organizations to cater to the common use cases you’ll encounter when building for B2B—from multi-tenant authentication use cases like org-specific, isolated tenants to enterprise SSO options like SAML, to role-based access control (RBAC).
"}},{"@type":"Question","name":"How does Clerk’s B2B data model support multi-tenancy?","acceptedAnswer":{"@type":"Answer","text":"
Clerk gives you a multi-tenant data model that maintains a hierarchical relationship between three core entities: organizations, members, and roles. Each organization has its own settings, roles, and members, while users can belong to multiple organizations with a single account. In cases when a user belongs to more than one organization, your app gets access to the active organization’s ID, metadata, and role context—so you can isolate data, enforce permissions, and structure your UI accordingly.
"}},{"@type":"Question","name":"What enterprise-level features can my app support with Clerk’s B2B Organizations?","acceptedAnswer":{"@type":"Answer","text":"
Clerk supports enterprise SSO protocols like SAML and even OIDC, meaning members can authenticate into organizations using their IdP-provisioned credentials from identity providers like Okta, Entra ID, and Google Workspace. We support role-based access control (RBAC) with default and custom roles for granular, tenant-specific permissions, alongside multi-factor authentication (MFA) using OTPs, TOTPs, passkeys, or biometrics to enforce secure access. With Verified Domains, you can restrict membership to specific email domains and enforce custom branding to streamline invitations and onboarding.
"}},{"@type":"Question","name":"How does multi-organization discovery vs. organization-specific authentication work with Clerk Organizations?","acceptedAnswer":{"@type":"Answer","text":"
Clerk supports both multi-org discovery and org-specific authentication by default. With <OrganizationSwitcher />, your users can sign in and seamlessly switch between all the organizations they belong to without any auth or data leakage between tenants. For org-specific authentication flows, Verified Domains let you restrict access to users with approved email domains (e.g., @company.com), automatically suggest relevant organizations during sign-up, and allow users to request to join or be automatically added to an organization based on their email. You can also use organization slugs (e.g., /acme) to route users to org-specific authZ flows/pages. Combined with support for SAML and other enterprise connections, these features make it easy to build smooth, secure discovery and onboarding experiences for B2B use cases.
"}},{"@type":"Question","name":"How does role assignment and membership work with Clerk’s Organizations?","acceptedAnswer":{"@type":"Answer","text":"
Clerk supports two default roles: admin and member. If you’re on the Organizations Add-on plan, you can also define custom roles and permissions to support more granular authorization logic. Roles and permissions for the user’s active organization are embedded directly in the session, so there’s no need to make a network request to fetch them. This makes it easy to run authorization checks in your frontend and any backend service you build. All membership settings, including invitations and role assignments, can be configured using <OrganizationProfile /> or Clerk’s APIs.
"}},{"@type":"Question","name":"Does Clerk support passwordless invitations?","acceptedAnswer":{"@type":"Answer","text":"
Yes. Invited users can sign up or sign in using magic links, passkeys, OTP, OAuth, or SSO, depending on your configured auth methods.
"}},{"@type":"Question","name":"How does Clerk Organizations work with Billing?","acceptedAnswer":{"@type":"Answer","text":"
Clerk Organizations integrates directly with Clerk Billing to manage subscriptions for SaaS apps without you having to write any custom payment logic. Using our <PricingTable /> component, you can display pricing plans on your app’s pricing page, enabling members and teams to subscribe instantly, with Clerk handling the entire subscription lifecycle, including plan upgrades, downgrades, and feature gating. You can gate features by plan using the has() method or <Protect /> component, so only subscribed members can access certain functionality. Clerk connects directly to your Stripe business account to sync users, payment methods, and transactions, and charges 0.7% per transaction (exclusive of your standard Stripe fees).
"}},{"@type":"Question","name":"What does pricing look like for Clerk Organizations?","acceptedAnswer":{"@type":"Answer","text":"
Clerk’s B2B/B2C SaaS features are available on both the Free and Pro plans, with optional advanced features offered through two add-on plans: the Organizations Add-on and the Authentication Add-on. The Free plan includes 100 monthly active organizations (MAOs) with up to 5 members per organization, and supports invitation flows and basic roles. The Pro plan costs $1 per MAO, with your first 100 MAOs free, and supports unlimited members per organization. The Organizations Add-on, available for $100 per month, includes support for verified domains and custom roles and permissions. The Authentication Add-on includes features such as multi-factor authentication (MFA), satellite domains, and enterprise connections.
"}}]}