Skip to main content
Paid Feature

This is a paid feature. Email us to get a license key to start a SuperTokens subscription.

If you want to try this feature without contacting us, you can sign up for our managed service, and use this feature in our development environment for free.

Multitenant login

Multitenant login is a feature that lets you customize the login experience for each of your customers. For example, a customer customer1 hosted on customer1.yourdomain.com can have passwordless login (using this recipe), and another customer customer2 hosted on customer2.yourdomain.com can have login with Active Directory and Facebook (using the thirdparty recipe).

Step 1: Create and configure a new tenant in SuperTokens core#

You can create a new tenant using our backend SDKs or via a cURL command to the core.

import Multitenancy from "supertokens-node/recipe/multitenancy";

async function createNewTenant() {

let resp = await Multitenancy.createOrUpdateTenant("customer1", {
passwordlessEnabled: true,
});

if (resp.createdNew) {
// new tenant was created
} else {
// existing tenant's config was modified.
}
}

Step 2: Build your multi tenant a UX flow#

The most common multi tenant flows are:

  • Tenants use a common domain to login: All tenants login using the same page (for example, example.com/auth) and are optionally redirected to their sub domain post login. At the start of the login flow, the customer will have to input their tenantId / workspace URL / identifier - as defined by you, and the login methods shown would be based on their tenantId.
  • Tenants use their sub domain to login: Here, each tenant has a sub domain assigned to them (for example customer1.example.com, customer2.example.com, ...), and they would visit their sub domain to login and access their app. Each sub domain's login experience may be different (as defined by you or the tenant).

SuperTokens is flexible enough to allow other forms of UX as well, but since the above two flow are most common, we provide dedicated docs for them (see the links above).

See also#