Skip to content
Esc
navigateopen⌘Jpreview
Dashboard
On this page

Introduction

Explore how you can implement enterprise authentication flows with SuperTokens.

Overview

Enable paid features

This feature is only available to paid users. Follow the instructions below to enable it.

Managed Service

  1. Sign in to the SuperTokens dashboard.
  2. Select the managed service option from the service type select component.
  3. Select your core instance from the next elemenet or create a new one.
  4. Open Features sub-page and enable the required ones.

Self Hosted

  1. Sign in to the SuperTokens dashboard.
  2. Select the self-hosted option from the service type select component.
  3. Select your license key from the next elemenet or create a new one. Then enable the required features.
  4. If the key is not yet configured, add it to your Core service. If your Core already uses this key, no configuration changes are required.

SuperTokens covers enterprise authentication scenarios through the multi-tenancy feature. Tenants represent isolated user groups that can only access their specific data. Furthermore, each tenant can have different methods of logging in, configured by the tenant, or by you (the application developer).

For example, a SaaS application for a financial company may want to separate their users by the financial institution they represent. This would require a login screen that asks for a username and password, as well as the name of the tenant. The application would then route the user to their specific tenant, which could be a different database or a different collection of data within a database.

Features

Feature Description
Enterprise SSO/SAML login Customers can log in with Workforce IdP or any other SSO provider
Unique login methods per tenant Each tenant can have its own login method (for example, email password login for one tenant, SSO login for another)
Different user pools Each tenant has its own isolated user pool. Users can use the same email across different tenants as separate accounts and you can share users across tenants.
Data isolation You can have separate databases per tenant
Dynamic tenant creation You can create tenants via API calls from your backend without manual onboarding
Multiple development environments Create multiple environments for development and CI/CD testing purposes
Flexible tenant discovery Authenticate users through different subdomains or based on a custom tenant selection

Getting started

The initial setup guide shows you how to create a tenant and configure authentication for it. After that, you have to implement the tenant discovery flow. Choose between the common domain login and subdomain login methods, based on your use case.

Before you explore the guides, read through the Important concepts page first. It explains how multi tenancy works in more detail.

Customization

To adjust the functionality to fit your use case you can explore different sections from the documentation.

API reference

API schema and response details