Proyecta Auth
Built-in user authentication. Email and Google login — with role-based access.
Proyecta Auth handles user authentication for the apps you build. Users click login or sign up, a Proyecta Auth page opens (in a popup by default), they choose their preferred method, authenticate, and return to your app signed in.
Supported login methods
Section titled “Supported login methods”| Method | Availability |
|---|---|
| All plans | |
| Email (one-time passcode) | All plans |
Add auth to your app
Section titled “Add auth to your app”Just ask the AI:
Add user authentication to my app with Google and email login.Show a profile menu in the header when the user is signed in.Enabling auth doesn’t hand-write a login system from scratch. The sign-in page, the OAuth callback handler, and the auth state hook (AuthProvider / useAuth) already ship in the app template. Auth is a capability you activate: when you ask, Proyecta provisions your app’s auth client, sets the sign-in configuration, and surfaces the pre-built sign-in UI (for example, a profile menu in your header) — so you get the template’s tested flow wired in, not improvised routes.
View your users
Section titled “View your users”Open your app’s own admin panel → Members to see everyone who has signed in and manage their access. (The builder’s old Users tab folded into the app’s admin.)
Roles and permissions
Section titled “Roles and permissions”Every app comes with a built-in role system — three levels, least to most access:
- User — any signed-in end user (the default for everyone who signs in).
- Staff — elevated access to the operational parts of your admin.
- Admin — full access, including managing other people’s roles.
You manage who has which role from your app’s admin panel → Members — promote or demote people there, and the server enforces every role check. The first admin is the email you designate when the app is created (see Admin Panel). You don’t build any of this — it ships with every app.
Can I use a custom auth provider instead of Proyecta Auth?
Proyecta Auth is the built-in provider and the supported path — it handles sign-in, the OAuth callback, and the session for you. Wiring an arbitrary third-party auth SDK into a generated app isn’t supported (the build blocks server-auth packages such as NextAuth and Supabase Auth). Enterprise SSO through your own identity provider is on the roadmap — see SSO & SAML.
Can I use in-app login flows instead of a redirect?
The default generated app uses a popup-based login flow — the Proyecta Auth page opens in a popup window rather than replacing the current page. A full redirect-based flow is also supported and can be requested from the AI.
Can I hide specific login methods?
Not yet. All enabled login methods are shown to users. Selective display is coming soon.
What if users aren’t receiving OTP emails?
Check spam folders, try an alternative login method or email address, or ask your IT team to whitelist proyecta.dev and notifications.proyecta.dev.
Can I impersonate a user for support?
Not yet. Use role-based access to build admin views that show user-specific data instead.
Coming soon
Section titled “Coming soon”- Login page branding — customize colors, logo, and layout to match your app’s brand
- Microsoft OAuth — sign in with a Microsoft account
- SAML / SSO — enterprise single sign-on (planned for the Studio plan)
- SMS OTP — one-time passcode via text message
- Email / password — traditional credentials with password reset flow
- Additional OAuth providers — GitHub, Apple, and more
- Selective login methods — choose which methods appear on the login page
- User impersonation — sign in as a user for debugging and support