(Optional) Require Auth for Onboarding Steps
Require that the user is logged in before visiting certain steps of your form, such as a post-login onboarding flow.
Last updated
Require that the user is logged in before visiting certain steps of your form, such as a post-login onboarding flow.
Last updated
Feathery's integrations provide support for multiple auth providers, but we will use Stytch for our examples here. Once you have set up your login and signup flow, you can revisit your auth integration settings to configure which steps in the form are only accessible after the user has logged in.
Do not make your login and signup steps inaccessible. The common use case for this pattern is to protect onboarding steps you want the user to see after logging in.
You can easily build a single Feathery form for login, signup, AND post-signup onboarding. We recommend using one of our auth integrations to disallow logged-out users from accessing your onboarding steps.
In the Integrations
tab, open Stytch to configure the settings for:
Authentication required for...
lets you select which form steps require authentication. Following this example, you would select all steps containing your onboarding questions.
Login Start Step
lets you configure which step the user is directed to after logging in. Following this example, you would select the first onboarding step.
Logout Start Step
lets you configure which step the user is directed to after logging out. Following this example, you would select the Sign In
step.
In the Flow
tab, you can see which steps are locked and protected by your authentication gate.