Apps you build with Vision can have real authentication — their own users, sessions, and permission levels. You don’t wire any of it by hand: describe what you need and the agent builds it on the project’s built-in database and backend.
Adding auth to your app
Ask for it like any other feature:
Add login and registration to my app. Store users in the database,
and only logged-in users can see the dashboard.The agent builds the pages, the session handling, and the user table, then protects the routes you named. Because every Vision project already includes a managed database and backend, there is nothing external to sign up for or connect.
What you can ask for
- Sign-up and login pages — email + password, styled to match your app
- Protected pages — “only logged-in users can see…”
- Roles — “admins can edit, everyone else can only view”
- Password reset and email verification — describe the flow you want
- Invite-only access — “no public sign-up; I add users myself”
Be explicit about the rules (“viewers can’t export data”) — auth rules make excellent guardrails, so the agent keeps enforcing them on every future change.
Your app’s users vs your Vision team
Two separate worlds, worth keeping straight:
- Teammates are the people building with you inside Vision.
- Your app’s users are whoever signs into the app you built — they live in your app’s database and never need Vision accounts.
Signing in to Vision itself
Your Vision account uses Google sign-in or email + password, and teammates join via email invites. Manage your own account in User profile and password.