How your app's users sign in

Every generated app signs people in with an email address and a six-digit code. There is no password to set or reset. Signing in with an address for the first time creates the account, so the app has no separate sign-up step.

1. Open the app’s Preview or Production address in a private browser window.
2. Open a part of the app that needs an account. A visitor who is not signed in sees “Sign in to continue” and a Sign in / Sign up button.
3. Choose the button, enter your email address and choose Send Code.
4. Enter the six-digit code in Verification Code and choose Verify. You return to the app signed in.
5. If a signed-in person opens an area their permissions do not cover, the app shows an access-denied view instead of the content. Offer them a different account, or grant the permission.

The sign-in page never asks for a password. A new code can be requested once a minute for each address.

Test sign-in

Use an address you can read, in a private window, so you see what a real person sees. Addresses that end in .test are reserved for automated tests. No email is ever sent to them, and the code is written to the sign-in service’s log instead, which customers cannot read. Do not rely on them for manual checks.

Preview and Production keep separate people. Someone who signed in to your Preview is a separate user in Production, with their own permissions. See Choose Preview or Production users.

Production sign-in for a self-hosted copy of your app is covered in Configure production sign-in. Back to the section overview.

Application example

Category: Project and task management. Example: Task Grove, a task board for a small team. A new teammate opens Task Grove, receives a code at their work address and lands in the task board after one verification.