Current BaseBuddy installs use local password sign-in stored in BaseBuddy app data.

Google OAuth is not an active sign-in provider in this setup model yet. Do not configure Google OAuth in Supabase expecting BaseBuddy login to use it.

What to use instead

Create users with the browser setup flow or CLI:

shpnpm basebuddy user:create \
  --email "editor@example.com" \
  --name "Editor" \
  --password "choose-a-strong-password"

Then add the user to a project through member settings or project invites.

Why Supabase settings do not apply

BaseBuddy app state lives in the selected app-data backend. Supabase-hosted users, sessions, redirect allow-lists, and OAuth providers are not the runtime source of truth for BaseBuddy login.

Verify the supported login flow

1. Run pnpm basebuddy doctor --skip-db-check.
2. Confirm Owner account and Environment values are ready.
3. Open /login.
4. Sign in with a local user email and password.

If you opened an old OAuth callback URL, return to /login and use password sign-in.

Related pages

• How to create local password sign-in users
• How to verify BaseBuddy sign-in setup
• Security