All use cases

Supabase Auth + Dashboard

Full auth flow with a protected admin panel.

DashboardsAgent: claudeModel: claude-sonnet-4-20250514
Integrated Services
Supabase
Required Configuration

This use case works best with the following environment variables, which are injected into your sandbox at runtime:

NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEY
Prompt
Build a Next.js dashboard app with Supabase auth (email/password + Google OAuth). Include: 1. Sign up, sign in, and password reset flows 2. Protected dashboard route with RLS-enabled data fetching 3. User profile page with avatar upload to Supabase Storage 4. Admin panel showing registered users count and activity metrics 5. Responsive sidebar navigation with shadcn/ui components Use Supabase JS client and Row Level Security policies throughout.
Use this

Why this exists

Auth is where side projects quietly die. Rolling your own is a security minefield, and the hosted identity platforms lock your user table inside their dashboard, then start metering monthly active users the moment you get traction. Supabase hands you Postgres, auth, and storage that you actually own, but stitching them into a real dashboard with correct Row Level Security is fiddly work most tutorials wave past. This blueprint does exactly that part, and hands you the code.

What the agent builds

A Next.js dashboard with Supabase auth covering the whole account lifecycle: sign up, sign in, password reset, and Google OAuth. Behind the login sits a protected dashboard route that fetches data through Row Level Security policies, so a user only ever reads their own rows. There's a profile page with avatar upload to Supabase Storage, an admin panel reporting registered-user counts and activity metrics, and a responsive sidebar built from shadcn/ui components.

You watch it happen in the task workspace: the agent scaffolds the app, wires the auth flows and RLS policies, builds the profile and admin pages, and starts the dev server to confirm a protected route redirects when logged out. The code lands on a branch in your repository with a pull request ready.

Make it yours

The first version is a starting point you steer with plain follow-up messages:

  • "Add GitHub as a third sign-in option."
  • "Require email verification before the dashboard unlocks."
  • "Add roles so only admins can open the admin panel."
  • "Let a user delete their own account and all their data."

Each follow-up wakes the same repository and the agent continues on its own code.

FAQ

Do I need a Supabase project? Yes, it runs on your own Supabase instance, so users, tables, and uploaded files all stay in your account.

Is the data actually protected? Yes, Row Level Security is enforced at the database level, not just hidden in the UI, so the rules hold even outside the app.

Can I add more sign-in providers? Yes, Supabase supports many. Ask the agent to enable another and it wires the button and callback.

Supabase Auth + Dashboard | OutcomeDev Use Cases