VibetaBack to setup

BUILD GUIDE · ACCOUNTS & SIGN-IN

Give your users an account.

Google login first. Add account email when you need it. This is a guided checklist, not an automatic connection to your providers.

Enter a project label to keep its checklist separate.

0 of 8 steps marked complete

Email steps are optional for Google-only apps. Progress is saved in this browser per project label; it does not verify your accounts.

Which service does what?
Code and revision history.Website hosting and server functions.Accounts and sessions; also Postgres data, file storage, realtime updates and Edge Functions.Verifies Google identity. Google login does not require Firebase.Delivers transactional account emails.AI responses, configured separately on the server.
ServiceJob in this setup
GitHub
Netlify
Supabase
Google
Resend
OpenAI

Supabase or Firebase?

Both provide authentication, databases, storage and backend functions. Supabase centers on relational Postgres. Firebase offers Firestore and Realtime Database, plus SQL Connect for PostgreSQL, hosting and mobile tools such as Crashlytics and Cloud Messaging. Choose for the app’s needs; a working Firebase app does not need to migrate just to use Google login.

1. Choose a dedicated project

Create or select a Supabase project for this app. In Google Cloud, select the matching app project before creating OAuth credentials. Reuse the workflow, not another app’s keys or project IDs.

Check: both dashboards show the intended app name.

2. Set the return address

In Supabase → Authentication → URL Configuration, set Site URL to your deployed HTTPS app address. Add the exact return URL used by your app to Redirect URLs. Save changes. These are app return addresses; Google’s callback below is different.

Check: the deployed origin and allowed return path match your app.

3. Create Google credentials

Open Google Cloud → Google Auth Platform. Complete Branding, support/contact email and Audience (External for public users). Under Clients, create a Web application—not Desktop app. Set the JavaScript origin to your deployed origin. Copy the callback from Supabase’s Google provider panel into Authorized redirect URIs: https://YOUR_PROJECT_REF.supabase.co/auth/v1/callback. Leave the AI-powered agent option unchecked for ordinary sign-in.

Check: correct project, Web application, exact Supabase callback. Review test-user restrictions and publishing status before inviting everyone.

4. Enable Google in Supabase

In Authentication → Sign In / Providers → Google, enable Google and paste the client ID and client secret directly from Google Cloud. Keep Skip nonce checks and Allow users without an email off. Save. Do not upload the OAuth JSON or paste secrets into chat.

Check: Google is enabled and credentials are saved. Users enter their Google password only on Google’s page.

5. Connect the app interface

Ask your coding tool to add Continue with Google using Supabase signInWithOAuth, provider google, and the approved redirectTo address. Handle the callback/session using the framework’s supported flow, plus loading, cancellation, errors and sign-out. Use only the project URL and publishable key in browser configuration. Configure server-only secrets separately.

Check: the deployed button opens Google, returns to the app and displays the signed-in account. Enabling the provider alone does not add a button.

6. Verify a sending domain (email route)

If offering email sign-in, add a domain you own in Resend → Domains. Use DNS auto-configuration when available, or copy the full, exact records Resend supplies into your DNS provider. Preserve existing mail records; receiving is not needed for outgoing account emails. Wait until the domain is Verified. An API key alone does not verify a domain.

Check: Resend shows Verified, not merely Pending. Never copy a shortened DKIM value from a screenshot.

7. Configure account email (email route)

Create a Resend API key with sending access for the domain. In Supabase → Authentication → Email → SMTP Settings, enable custom SMTP. Sender: noreply@YOUR_VERIFIED_DOMAIN; name: your app. Host: smtp.resend.com; port: 465 (TLS); username: resend; password: the Resend API key. Save. Enable Email signup and confirmation if using confirmed email accounts.

Check: request an actual account email, confirm delivery, then complete sign-in. A saved configuration is not proof of delivery. For PKCE magic links, use the browser that requested the link.

8. Verify access, not just the redirect

Test a new account, returning sign-in, page reload, sign-out, cancellation and a failed/expired link. Check provider logs for failures. Test email separately if offered. Before storing private user data, add tables and Row Level Security policies that enforce ownership; test that account A cannot read or modify account B’s data.

Check: record what actually passed. Login does not automatically implement saved projects, votes, subscriptions or permission rules.

When something goes wrong
What we learned from Woodynews

Google sign-in was confirmed working by the app owner. The sending domain was verified. Email sign-in encountered a generic failure and still needs a separate successful delivery-and-login test. Cross-device preference persistence and account-isolation checks are separate acceptance checks.

The reusable lessons: dedicated projects, a Web OAuth client, the exact callback, verified transactional email and a real end-to-end test. This guide does not enable authentication in Vibeta itself.

Keep client secrets, SMTP keys and Supabase secret/service-role keys out of chat, screenshots, GitHub and browser code. User-editable profile metadata must not decide access permissions.