Sign-in for your app's users
Every project has its own user pool with passwords, magic links and one-time codes. Manage people from the Users tab.
Key takeaways
- People sign in to your app with a password, or with a magic link or 6-digit code by email.
- Each project has its own users: the same email in two projects is two users.
- Five wrong passwords lock an account for 15 minutes.
- Someone who never confirms their email is deleted 7 days after their last email, and can sign up again.
Open Users
Open the project and choose Users. The switch at the top moves between Users, Sign-ins and Email.
Help someone sign in
From a user's row: Send a reset link, or Sign out everywhere. A locked user shows why and until when, and owners can unlock them right away. An unverified user can get the email again.
Watch sign-ins
Sign-ins lists every event, newest first, with failures in red, the method and where it came from. Filter to failed only, sign-ups or password resets. Events are kept 90 days.
Remove a user
An owner of the workspace can delete one of its project's users. That ends their sessions, and your app's own rows stay as they are.
Sign people in from your server
If your app's server makes the sign-in calls, send its `SCAFFOLD_AUTH_SECRET` as `Scaffold-App-Secret` and each person's address as `Scaffold-Client-Ip`, or use the SDK's `clientIp`. Each person then gets their own rate limits instead of everyone sharing your server's. Only your server holds the secret, so no browser can pass an address.
Take your users elsewhere
An owner chooses Export on the Users tab to download every user as JSON, with the password hash of each one who set a password, so they sign in to your next auth system with the password they have. Users who sign in only by link or code have no password to export.
The export format
The file holds project_id, exported_at and users. Each user has id, email, name, email_confirmed_at, created_at and password, which is null for a user without one. A password holds algorithm (argon2id), version (19), memory_kib, iterations, parallelism, salt and hash, the last two in unpadded standard base64, and phc: the same hash as one PHC string, like $argon2id$v=19$m=19456,t=2,p=1$salt$hash.
Most auth systems import an Argon2id PHC string as it is. To check one yourself, give phc and the password to any Argon2 library's verify, like argon2.verify(phc, password) from the argon2 package in Node or PasswordHasher().verify(phc, password) from argon2-cffi in Python. A system that takes the parts runs Argon2id over the password and the decoded salt with memory_kib, iterations and parallelism, as IDKey in Go's golang.org/x/crypto/argon2 does, and compares the result with the decoded hash.