Skip to content
Scalekit Docs

Organization switching and access control

Organization switching allows users to access multiple organizations or workspaces within your application. This feature is essential for B2B applications where users may belong to several organizations simultaneously, such as their own company and client organizations they work with.

Common organization switching scenarios

Section titled “Common organization switching scenarios”

Personal workspace to corporate workspace

A user might sign up for your app using their organization’s email address, which creates their personal workspace. Later, when their organization subscribes to your app, a new corporate workspace is created (for example, “AcmeCorp workspace”).

Scalekit automatically detects when users belong to multiple organizations and presents them with an organization switcher. Users can then choose which workspace to access when signing into your app.

Multi-organization contractors

Many organizations work with external consultants or contractors who may belong to multiple organizations, each with their own SSO authentication policies. These users need to seamlessly switch between different client organizations while maintaining secure access to each workspace.

How Scalekit handles organization switching

Section titled “How Scalekit handles organization switching”
  1. Users click Sign In on your application.
  2. Your application redirects users to the sign-in page.
  3. Users authenticate using one of the available sign-in methods.
  4. Scalekit displays a list of organizations that users belong to.
  5. Users select the organization that they want to sign in to.
  6. Users are redirected to the organization’s workspace and signed in.

Scalekit provides built-in support for organization switching through the following features:

  • Automatic organization detection: Scalekit identifies all organizations a user belongs to based on their email domain and invitation status
  • Organization switcher UI: Users see a list of available organizations when signing in
  • Cross-organization authentication: Users can access multiple organizations with different authentication policies Coming soon
  • Secure session management: Each organization maintains its own authentication context and policies

What’s next?

Section titled “What’s next?”