Clarification on auth.users
We are currently developing a Flutter app and a ReactAdmin based admin web tool. I'm not really sure on how to use the auth.users table.
It would make a lot of sense to me to use the auth.users table as the table for admin users (meaning the users that can log in to the website; they are created & invited via the supabase app console) and then create a new public.users table for the app users.
But that does not seem to be the preferred way to do it when reading the documentation (i.e. the login/auth functionality for the app will also have to use auth.users as far as I can see). To store further fields for these app users, you would then have to add the public.users table and join it via primary key to auth.users.
Am I understanding this correctly? Because that way you would not have good separation between two very different types of users? That seems like a very poor design decision to me. Some clarification would be very much appreciated
It would make a lot of sense to me to use the auth.users table as the table for admin users (meaning the users that can log in to the website; they are created & invited via the supabase app console) and then create a new public.users table for the app users.
But that does not seem to be the preferred way to do it when reading the documentation (i.e. the login/auth functionality for the app will also have to use auth.users as far as I can see). To store further fields for these app users, you would then have to add the public.users table and join it via primary key to auth.users.
Am I understanding this correctly? Because that way you would not have good separation between two very different types of users? That seems like a very poor design decision to me. Some clarification would be very much appreciated
