# New Supabase mini-course **URL:** \ **Category:** Tutorials\ **Tags:** supabase\ **Created:** [September 20, 2023, 1:18pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464 "2023-09-20T13:18:26Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [September 20, 2023, 1:18pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/1 "2023-09-20T13:18:26Z")
Hey there 👋 Thought you’d like to know we just started a new YouTube playlist dedicated to [WeWeb + Supabase tutorials](https://www.youtube.com/playlist?list=PLvTqMLG5UNf4ny-AhRX_hIMgUUyrQ0QFd) 🙂 Here’s what you can expect: - [get and display Supabase data](https://youtu.be/PwI7pPWULkg) in WeWeb (includes info about Row-Level Security) - [update Supabase records](https://youtu.be/sOhq48G4wsQ) via WeWeb - signup and login [with email and password](https://youtu.be/pJgwMv-1dPs) - signup and login [with a provider](https://youtu.be/pHkkD2FFOWM) (e.g. Google or Slack) - setup a [forgot password flow](https://youtu.be/-6ENPyuUDUY) - create and update custom [user metadata](https://youtu.be/F-67cGm7kdk) - setup [users / profiles synchronization in Supabase](https://youtu.be/dK835d1CWYo) to allow users to view & edit other user’s information (includes info about Row-Level Security to ensure you keep this secure!) If there’s anything else you’d like to see in there, let us know! ---
**Author:** ![david](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@david](https://community.weweb.io/u/david)\ **Post date:** [September 20, 2023, 1:42pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/4 "2023-09-20T13:42:03Z")
Static Pages @Joyce ---
**Author:** ![JamesPan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/jamespan/32/3594_2.png) [@JamesPan](https://community.weweb.io/u/JamesPan)\ **Post date:** [September 21, 2023, 11:12pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/6 "2023-09-21T23:12:19Z")
Thank you. Will take the time to check out this coming weekend. ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [September 25, 2023, 4:55pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/7 "2023-09-25T16:55:33Z")
Hey @david 👋 Great idea! Not sure I will have the time to do a full tutorial on this in the coming weeks but I just answered in this thread to help you get started: [Static Pages + Supabase - #15 by Joyce](https://community.weweb.io/t/static-pages-supabase/4442/15) ---
**Author:** ![sebschaeffer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/sebschaeffer/32/7089_2.png) [@sebschaeffer](https://community.weweb.io/u/sebschaeffer)\ **Post date:** [January 14, 2024, 5:13pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/8 "2024-01-14T17:13:06Z")
@Joyce great tutorials, thank you! I am a bit confused about the user data handling, especially public vs auth. It seems we can update auth user metadata directly from weweb so what is the benefit of having a public profiles table? Especially since supabase auth provides user metadata on login but I would have to query the DB for the public profile after login and make it persistent (store it in a global variable maybe?). I am curious what the best practice is here, especially: - When to store data in auth user metadata - When to store data in public profile table - best practice on making public profile table persistent (or should I query the db whenever I need data like avatar url etc?) thanks! 🙂 ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [January 18, 2024, 2:36pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/9 "2024-01-18T14:36:15Z")
Hi @sebschaeffer 👋 > [@sebschaeffer](#): > > what is the benefit of having a public profiles table This is helpful if you want users of your app to view other user data, i.e. not just their own info (e.g. a social media app) or if you need a view where admins can see/edit/delete user data (e.g. a company directory where the HR team can edit other users’ information). In both cases, the users in the `auth` schema contain the information needed for authentication (and may contain additional info in the metadata if you’d like) but the profiles in the `public` schema can contain a lot more information and you can fine tune what people can or cannot do with the data in that table. Does that help? ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [January 18, 2024, 9:44pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/10 "2024-01-18T21:44:50Z")
You can actually read everything about it from Supabase directly, they encourage you to do what Joyce does in the video, because this way it’s more handy in general. > **[Managing User Data | Supabase Docs](https://supabase.com/docs/guides/auth/managing-user-data)** > > Securing your user data with Row Level Security. ---
**Author:** ![ianc](https://avatars.discourse-cdn.com/v4/letter/i/5f8ce5/32.png) [@ianc](https://community.weweb.io/u/ianc)\ **Post date:** [January 24, 2024, 11:59pm UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/11 "2024-01-24T23:59:35Z")
Hi, I’m new and not that experienced. Started with Bubble, and managed okay but after some research I thought WeWeb might be a better option. Further research also suggested using Supabase might be a better option than some of the others. I’ve got my head around some of the basic functionality of connecting a Supabase table (using the Supabase plugin) to create a collection and using repeat items and simple formulas to populate text fields. And now I’ve just found this, which will be really useful. What I’d like to see is how to relate one table to another for a specific purpose. In my scenario the user would create a project table that holds simple high level base data on a house/property (address and contact details etc) and then they would add standard descriptions of each room (dimensions, images etc). I’m interested in how the tables in Supabase and the structure of WeWeb would work. I’d like to see a video on this. In my minds eye I see a card that holds the property details and when the user clicks on it, a list of rooms is revealed with relevant data. Is there a chance you could put together a video on how this is achieved, please? ---
**Author:** ![ianc](https://avatars.discourse-cdn.com/v4/letter/i/5f8ce5/32.png) [@ianc](https://community.weweb.io/u/ianc)\ **Post date:** [January 25, 2024, 12:02am UTC](https://community.weweb.io/t/new-supabase-mini-course/4464/12 "2024-01-25T00:02:47Z")
Just to clarify, I think this should be two tables? One for each house and one for each room. Each house has many rooms.