Builder Settings
Auth Session
Control how signed-in users are remembered and where they land after authentication, so launch behavior and login flow stay consistent for real users.
Choose whether users stay signed in across launches.
Skip auth entry if a valid session already exists.
Select where authenticated users should be routed.
Session and routing controls
Remember signed-in users
Enable persistence (persistSession) so users are not required to sign in every app launch.
Skip auth on valid session
Enable automatic launch into authenticated flow when session state is valid.
Choose landing destination
Route signed-in users to a global screen or per-auth-component destination strategy.
Depend on screen availability
Landing options are driven by available non-auth screens from Manage Screens.
Configure auth session in five steps
Configuration flow
- Open App Settings & Deploy → Auth Session.
- Enable or disable Remember signed-in users.
- Optionally enable Skip auth screen when already signed in.
- Choose signed-in landing behavior and target screen.
- Save changes.
Recommended setup
- Enable persistence for production-ready UX.
- Set an explicit non-auth landing screen.
- Preview launch behavior with valid and invalid session states.
Common mistakes to avoid
Setting auto-open without persistence
Without persisted sessions, auto-open has no stable authenticated state to use on launch.
Missing landing destination
Always choose a valid non-auth screen to avoid ambiguous post-login routing.
Not testing both states
Validate behavior for first-time users and returning signed-in users before publishing.