Granular control over the auth flow with a multi-tenancy e-commerce store
Hey,
I am building a multi-tenancy e-commerce store, where the owners would be able to create stores and the customers for those stores would be able to create an account for each store.
To implement the flow where customers for those stores would be able to create an account for each one of those stores, I need granular control over the auth flow as I need to determine whether the user already has an account on supabase, and if they do then I need to associate them with a particular store. I am currently doing this with the supabase.auth.admin.createUser() method, but it does not seem very idiomatic as it is lacking email confirmation and I cannot implement the same flow for OAuth.
What would be the recommended/best way to achieve this by using Supabase? Or is supabase the wrong tool for this job?
Thank you!
I am building a multi-tenancy e-commerce store, where the owners would be able to create stores and the customers for those stores would be able to create an account for each store.
To implement the flow where customers for those stores would be able to create an account for each one of those stores, I need granular control over the auth flow as I need to determine whether the user already has an account on supabase, and if they do then I need to associate them with a particular store. I am currently doing this with the supabase.auth.admin.createUser() method, but it does not seem very idiomatic as it is lacking email confirmation and I cannot implement the same flow for OAuth.
What would be the recommended/best way to achieve this by using Supabase? Or is supabase the wrong tool for this job?
Thank you!
