December 19, 2025
Full stack Auth

Provision users into existing organizations with interceptors

Provision users into existing organizations at signup using interceptors—route users by email domain, map attributes, and avoid duplicate org creation.

Forr moderb B2B AI apps, not every signup should create a new organization.

Default auth flows often treat every new user as a new tenant, leading to duplicate orgs and messy identity data. Scalekit lets you control this behavior directly during authentication.

With Pre-signup interceptors, you can provision users into an existing organization at signup—before a new org is created.

Route users by email domain

A common pattern is domain-based provisioning:

  • A user signs up
  • The Pre-signup interceptor runs
  • If the email domain matches a known customer, the user is added to the existing organization
  • If no match is found, the flow falls back to creating a new organization

This keeps tenancy clean, prevents duplicate orgs, and works seamlessly for both new and existing customers.

Identity decisions at the right boundary

By enforcing provisioning rules inside the auth layer, you avoid post-login fixes, background reconciliation, and edge cases that grow with scale. Users land in the right organization from their very first session.

👉 Get started with Full Stack Authentication
https://docs.scalekit.com/authenticate/fsa/quickstart/

Share on

Provision users into existing organizations with interceptors

Forr moderb B2B AI apps, not every signup should create a new organization.

Default auth flows often treat every new user as a new tenant, leading to duplicate orgs and messy identity data. Scalekit lets you control this behavior directly during authentication.

With Pre-signup interceptors, you can provision users into an existing organization at signup—before a new org is created.

Route users by email domain

A common pattern is domain-based provisioning:

  • A user signs up
  • The Pre-signup interceptor runs
  • If the email domain matches a known customer, the user is added to the existing organization
  • If no match is found, the flow falls back to creating a new organization

This keeps tenancy clean, prevents duplicate orgs, and works seamlessly for both new and existing customers.

Identity decisions at the right boundary

By enforcing provisioning rules inside the auth layer, you avoid post-login fixes, background reconciliation, and edge cases that grow with scale. Users land in the right organization from their very first session.

👉 Get started with Full Stack Authentication
https://docs.scalekit.com/authenticate/fsa/quickstart/

Schedule a demo with Scalekit today.