An auth experience in an app can be built in many ways. Experiences vary in the steps a user needs to take and the UI / UX experience of each step.

Traditionally, solutions provide one auth experience that has everything and the user can toggle on / off each element, however, that sometimes result in restrictions or in an overkill experience for the developer.

To keep things simple and flexible, we have come up with a "Recipe" based auth solution. A Recipe is a combination of Auth steps, UX and UI that the user experiences. Some examples of recipes are:

See more examples here

Technical Architecture

Overall Architecture

EmailPassword Frontend Module

EmailPassword Backend module

Core architecture change

Third party Login

Third Party with email password

Documentation structure

Dashboard (v3.2+)

Enabling multi tenancy for b2b apps