The Jet Admin Supabase Auth integration lets your app authenticate users against the same accounts already stored in Supabase, driven by the same roles and permissions you already manage in Jet. Whether you're adding an admin panel on top of a Supabase-backed product or opening a portal to its existing users, the whole sign-in flow runs off Supabase's own user table.

That covers what teams build with Supabase Auth first: internal admin panels for a product already running on Supabase, and customer portals for users who already have an account there. Because Jet reads the role or plan field you already store in Supabase, permissions stay correct without a second user table to maintain.

Key benefits

• One user table. Authenticate against the accounts already in Supabase, with nothing to duplicate.
• Fast to launch. Ship an admin panel on a Supabase-backed product without building a separate login system.
• Roles from existing data. Reuse a role or plan field you already store, instead of maintaining a second permissions system.
• Self-service sign-up. Register new Supabase users directly from a Jet form when you need to.
• Stays in sync. A profile change in Supabase is reflected in Jet on the next login.

How to connect Jet Admin with Supabase Auth

1. In Supabase, open Project Settings → API and copy your project URL and anon key.
2. In Jet Admin, open your app's authentication settings and choose Supabase Auth.
3. Enter your Supabase project URL and API key.
4. Map the role or plan field in Supabase to roles inside your Jet app.
5. Test sign-in with an existing Supabase account to confirm the mapping is correct.
6. Publish the app and share the login link with your users.