# Example: Supabase Auth, Quick Setup & Login **URL:** \ **Category:** Tutorials\ **Tags:** supabase\ **Created:** [April 30, 2025, 4:00pm UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052 "2025-04-30T16:00:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dhew](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dhew](https://community.weweb.io/u/dhew)\ **Post date:** [April 30, 2025, 4:00pm UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052/1 "2025-04-30T16:00:10Z")
Quick start for Supabase Auth implementation…after setting up Supabase Auth plugin. In Supabase, there are important settings in the active Auth Providers: ![Screenshot 2025-04-30 at 11.05.00 AM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/9c3601073db003d9c9d97726fc7093b28367ae5a.png) Disable “Confirm email” (in the email Auth Provider) if you want to create a user (in WeWeb’s Supabase Auth plugin interface) and then login as that user (e.g., to test access control policies while in development): ![Screenshot 2025-04-30 at 11.04.35 AM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/fbdfd8f6d7f3b6d011cbd63f0c69ae24ea6798a0.jpeg) The default/‘starter’ login components in WeWeb are not fully functioning out of the box, even though they have a workflow attached. ![Screenshot 2025-04-30 at 11.06.59 AM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/e/e9e00fbc1653b1a05dae61f1960f4ff200007f41.png) WeWeb example components use Xano. Remove that workflow step and replace with the “Sign In” one for Supabase Auth (and add the form fields to the workflow action): ![Screenshot 2025-04-30 at 11.12.41 AM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/4/4f9769d4e724c3ed0a11a4c65d5d1f81c080839f.png) Tip: Build a simple “profile” page to ensure you are logged in as the intended user: ![Screenshot 2025-04-30 at 11.11.17 AM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/07fe09c90118d7f0e2b122a97641f5ffb50806ad.jpeg) Hope it helps you build faster. ---
**Author:** ![emdiemeric](https://avatars.discourse-cdn.com/v4/letter/e/e9bcb4/32.png) [@emdiemeric](https://community.weweb.io/u/emdiemeric)\ **Post date:** [May 1, 2025, 12:25pm UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052/2 "2025-05-01T12:25:34Z")
For assigning Roles, do we still need a separate table? i.e. User, Super User, Admin ---
**Author:** ![dhew](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dhew](https://community.weweb.io/u/dhew)\ **Post date:** [May 1, 2025, 12:49pm UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052/3 "2025-05-01T12:49:47Z")
If you plan on using roles elsewhere in your app, then yes. This quick tutorial assumes you have already setup the Supabase Auth plugin, which is when you would typically do role table setup (see [WeWeb docs here](https://docs.weweb.io/plugins/auth-systems/supabase-auth.html)). Note: the docs are a bit behind–the current Auth plugin can do the role table setup for you. ---
**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\ **Post date:** [May 2, 2025, 11:48am UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052/4 "2025-05-02T11:48:20Z")
Hey Dhew! Thanks a lot for this tutorial! Removing Supabase’s email validation is excellent to learn without facing some auth issues. As for the example components, we do have ready-to-use components with supabase already working in the workflow. Steps: 1- Install Supabase plugin + Supabase Auth Plugin 2- Click on Add 3- Click on Supabase Auth button in the left column 4- Any component you use here will have supabase already integrated. ![Screenshot 2025-05-02 at 08.44.45](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/4/49404c27983641536b66077933e8c39acdc06538.png) ![Screenshot 2025-05-02 at 08.47.36](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/e/e5b3678a7f5c066bd22685dccdb40204d0f5dbee.png) ---
**Author:** ![dhew](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dhew](https://community.weweb.io/u/dhew)\ **Post date:** [May 2, 2025, 12:41pm UTC](https://community.weweb.io/t/example-supabase-auth-quick-setup-login/18052/5 "2025-05-02T12:41:22Z")
Hi Agustin, Good point. I think when I started this new project I had selected to start with the simple CRUD template, which came with some basic pages. One of those prebuilt pages was a login page that had the Xano workflow. So advice for Supabase users is to simply doublecheck any components you use to ensure they are using the Supabase workflow actions (and/or to just start with the Supabase Auth plugin components!). Thanks