Sign-in for your app's users
This page is about the people who use the app you built — not about your own Berrybell login. Turn this on and your app gets sign-up, sign-in, sessions and a Users dashboard. Projects from a template that comes with sign-in already have the screens; on any other project, the builder can add them when you ask — see If your app has no sign-in screens yet.
Turning it on
- Open your project settings and go to Cloud → Auth.
- Press Enable sign-in. If sign-in was on before, the button reads Turn sign-in back on.
- On a project with other environments, Berrybell asks Turn on sign-in for production? before it starts. Press Turn on for production.
You need the workspace Admin role. The panel shows Setting up sign-in… while it works, which takes up to a minute — leave the tab open.
Berrybell creates the accounts, sessions and verification tables inside your own project database — so your users' passwords live in your database, not in a Berrybell one. It takes a snapshot first, labelled Before enabling end-user auth, so the step is restorable.
The Admin / internal tool, Directory / marketplace, Form / waitlist and SaaS dashboard templates set this up when you create the project. See Templates that come with sign-in.
What has to be true first
Sign-in can't be turned on — the panel says Sign-in is not available for this project yet and gives the reason — when:
- Your workspace is on the free plan. End-user sign-in is a paid-plan feature.
- The project has no project database, or it isn't Ready yet.
On a project with other environments, the tables are created on production only, which is why you're asked to confirm the production change. Environments created or reset before that are copies without the tables. Right after you turn sign-in on, the panel names them. For an environment called staging it reads: "Production has the sign-in tables now. staging doesn't have them yet: reset it to copy the sign-in tables." The note isn't shown again once you leave the page, and that environment's Users tab says its database has no sign-in tables. Reset each one. A reset replaces that environment's database with a fresh copy of production.
Berrybell can also suspend end-user auth for a project. The panel then shows Sign-in is suspended for this project instead of Enable sign-in, and nothing you do in the panel lifts a suspension — contact support.
If your app has no sign-in screens yet
Turning sign-in on creates the tables but doesn't change your app's code. On a project built from scratch, or from any template other than those four, the app has no sign-in screens to use them, so the panel says so:
- The header shows Not in your app yet instead of Sign-in on.
- A banner reads Your app doesn't have sign-in in it yet.
- A visitor who tries to sign in is told sign-in isn't enabled.
Press Add sign-in to my app to send the builder that request in the chat. It runs as a normal build. The Google, single sign-on and two-factor settings stay hidden until your app has sign-in.
If you ask the builder for sign-in while it's off, it asks you to turn it on in Cloud → Auth first. It can't turn it on for you.
Turning it off is safe
At the bottom of the Settings tab, the row Turn off sign-in — stops new sessions. Accounts are kept, not deleted. has a Turn off button. The confirmation spells out what happens: everyone signed in is signed out and no new sessions are issued. The tables are deliberately not dropped. Every account survives, and turning it back on restores them.
If the tables go missing
The panel checks your live database rather than trusting a stored record. If the auth tables aren't there, it warns you that every sign-in will fail and offers Restore tables. On a project with other environments, it asks the same production question first.
The Users dashboard
Once sign-in is on, Cloud → Auth has three tabs: Settings, Users and Admin trail.
The Users tab lists everyone who has signed up, with search, a chart of sign-ups over time and 24-hour / 7-day / 30-day totals. Columns: Email, Name, App role, Sign-in, Created, Last seen and Status. Status shows a Banned, 2FA, Unverified or Signed in badge where one applies, and an open row shows the person's live session count.
It's the start of the person's newest session, not a last-activity timestamp, and it disappears when they sign out or are banned.
Open a row for the actions on that account:
- Ban / Lift ban, with an optional reason. Banning ends their sessions.
- Force password reset. This clears their password and every session, and sends no email — you have to tell them. To get back in they need your app's "Forgot password" flow, which only works once you've set up a sender and published. If they also sign in with Google, that still works.
- Turn off two-factor for someone locked out of it — see Two-factor authentication.
- Make app admin / Remove app admin — sets their role in your app,
useroradmin. It isn't a Berrybell role. - Export JSON — their account, linked sign-in methods and sessions as a file, for a subject-access request. It doesn't include data your app stores about them in its own tables.
- Delete the account permanently. You retype their email address to confirm.
Two buttons above the table act on more than one account:
- Sign everyone out ends every session at once. No account or password changes.
- Clear failed sign-ups appears when there are leftover rows from sign-ups that never completed. Each one locks its email address out of registering again until it's deleted. It deletes only rows older than the grace period shown beside it, so a sign-up still in progress is never touched.
Every one of these is recorded in the Admin trail tab: who did it, when, from what IP address, and the reason typed.
Impersonating one of your users is deliberately not offered.
While production is selected, your preview URL shares your live database. Anyone who signs up on the preview gets a real account in your live app.
Who can do what
Reading the Users list and a user's detail needs the Editor role. Every action above, and the Admin trail itself, needs workspace Admin. Workspace Admin is also needed to turn sign-in on or off, set up Google, allow a sign-in method in another environment, and make any change in Cloud → Email.
Two-factor authentication
Two-factor ships in the templates that come with sign-in: an enrolment page, a challenge at sign-in, and ten backup codes. Each of your users opts in themselves — there's no switch for it in the Studio.
Worth knowing:
- It covers password sign-in only. Someone signing in with Google keeps Google's own second step.
- Recovery is the backup codes first. After those, Turn off two-factor in the Users tab is the only route — and nothing is emailed either way, so you have to tell the person yourself.
- The panel checks per project. A project that turned sign-in on before two-factor shipped may not have the two-factor table. The Users tab then doesn't offer Turn off two-factor, and turning sign-in off and on again doesn't add it.
Google sign-in
Paste the client ID and secret from your own Google Cloud OAuth client into the Sign in with Google card. Like the other sign-in method cards, it starts folded; open it to see its settings. Berrybell shows the exact redirect URIs to register there, and verifies the credentials against Google before saving. Because it's your Google client, there's no Berrybell charge for it.
Two things trip people up:
- The redirect URIs only exist once your app is published. Publish first, then come back and set Google up.
- A custom domain added afterwards is a new origin Google doesn't know about. Sign-in on that address fails on Google's own page, and nothing errors in Berrybell. The Sign in with Google card does flag it: it opens by itself with Your app has a new address that Google does not know about and lists the URI to add. Register the new redirect URI when you attach the domain.
The automatic preview and the dev server are never given the Google, single sign-on or sign-in email settings. The Google button doesn't work there, and "Forgot password" and confirmation emails don't send. Email and password sign-in works. While production is selected the preview uses your live database, but it keeps its own sessions, so signing in there doesn't sign anyone in on your published site.
Email is a prerequisite for verification and resets
Email verification and "Forgot password" both need a sending address you own. Set one up in Cloud → Email — see Custom email domain. The Auth emails box on the Settings tab has an Open Email settings button that takes you there.
After you set a sender, publish once. Your live app is given the email settings when it's published, so it sends nothing until then. Until email is configured and published, a password-reset link has nowhere to go, so forcing a password reset only unblocks someone once email is set up and published.
In other environments, email is off until you turn it on for that environment and then publish to it. Until then "Forgot password" fails there. The Auth emails box says so while another environment is selected. See Environments and the preview.
Your app sends the two fixed authentication emails through that address, by design — it isn't a general-purpose sending rail.
Sign-in in other environments
On a Business project with environments, sign-in is turned on and off for the whole project, and the checks at the top of Cloud → Auth — whether sign-in is on, whether the tables exist, whether your app has sign-in in it — describe production. The Users list and the sign-in methods follow the environment selected in the top bar.
- Users. Another environment's Users tab lists that environment's own accounts. Its database started as a copy of production's, so the same people can appear, but banning, deleting or signing people out there doesn't touch production. The Admin trail covers the whole project, so entries from every environment appear together. It doesn't show which environment each entry acted on.
- Sign-in address. Each environment has a Sign-in address: its active custom domain, or its Berrybell address if it has none. Its sign-in links, and the addresses Google and single sign-on send people back to, are built from it.
- Google and single sign-on show Production only until you press Allow in this environment. The environment uses production's Google client and production's single sign-on connection, so nothing can be allowed until production has it set up — do that while production is selected. For Google, the panel first lists that environment's redirect URI to add to production's OAuth client, and you confirm with I've added it. Allow Google sign-in.
- When it takes effect. Allowing reaches the environment the next time you publish to it. After Turn off in this environment, Google keeps working there until you publish that environment again. Production isn't affected either way, and accounts created in the environment are kept.
- Email is off in an environment until you turn it on there and publish to it — see Email is a prerequisite.