Switch tenant context
A SaaS dashboard serves multiple customer workspaces and users need to change workspace context.
Clerk · Component
OrganizationSwitcher
OrganizationSwitcher is a Clerk component for multi-tenant apps. It lets signed-in users create, switch between, and manage organizations from the application UI.
How it works
OrganizationSwitcher is a prebuilt Clerk UI component for applications that use Organizations. It presents the signed-in user with controls to create an organization, switch the active organization, and manage organization settings, making organization context readily available in app navigation.
Syntax
<OrganizationSwitcher />Returns
Renders a Clerk organization switcher UI component.
Key points
- Use the component as the primary in-app UI for organization creation, switching, and management.
- Organizations provide a boundary for grouping users and assigning roles and permissions.
- The switcher combines organization lifecycle actions with active-context selection in one UI surface.
Common mistakes
- Place the component in persistent navigation when users need frequent access to organization context.
- When enabling Organizations, decide whether every user must belong to an organization; this setting affects how users enter the organization workflow.
Example: Add an organization switcher
import { OrganizationSwitcher } from '@clerk/nextjs'
export default function Header() {
return <OrganizationSwitcher />
}Render it in a header or navigation so signed-in users can create, switch between, and manage their organizations.
When to use it
Create an organization
A user needs to start a new team directly inside the product.
Manage organization access
An application gives organization members a central place to manage their current organization.
Interview questions
QWhat problem does OrganizationSwitcher solve?
OrganizationSwitcher is a prebuilt component that lets users create, switch between, and manage Organizations. It is intended for multi-tenant applications where users work in different organization contexts.
Follow-up: How would you expose the active organization outside the component? Use Clerk's organization APIs or hooks to read the current active organization and apply that context to application data and authorization.
QWhere should OrganizationSwitcher usually be rendered?
The component should generally be placed in an application's header or navigation. That placement keeps organization switching available while users move through the application.
Follow-up: What design concern follows from this placement? The surrounding layout should provide enough space for the switcher and preserve access on responsive screen sizes.
QHow does switching relate to multi-tenancy?
Organizations group users with roles and permissions for multi-tenant applications. Users can belong to multiple organizations, and the switcher changes which organization is active in the session context.
Follow-up: How can the active organization be used server-side? In a Next.js application, use Clerk's server-side client to retrieve organization information for the active organization or an organization ID.
Related
CreateOrganizationOrganizationProfileOrganizationListInviteMembersButtonuseOrganizationclerkClientOrganizations