2
Accounts/Teams
Source: supabase/supabase#756 · opened by @joshnuss
It might be worth having the concept of "Accounts", in addition to "Users".
It would make it possible to have teams of users for SaaS apps (multiple users per account) and still be able to use RLS.
Though, it may complicate things a bit, for example, what happens if a user has access to multiple accounts? Maybe the policy checks an array of account_ids, ie CREATE POLICY ... USING (account_id in auth.account_ids())
Caveat: It may create noise for apps that only need one level of identity. Though this kind of feature is tricky to bolt on later.
It would make it possible to have teams of users for SaaS apps (multiple users per account) and still be able to use RLS.
Though, it may complicate things a bit, for example, what happens if a user has access to multiple accounts? Maybe the policy checks an array of account_ids, ie CREATE POLICY ... USING (account_id in auth.account_ids())
Caveat: It may create noise for apps that only need one level of identity. Though this kind of feature is tricky to bolt on later.
No pledges yet. Be the first to back this.
Comments
Similar requests
Optional Flag to Allow SSO Identity Linking
4 votes · 0 comments
Is it possible to have multiple app-specific accounts using the same email in one Supabase project?
1 vote · 0 comments
Use the dashboard with any postgres role
1 vote · 0 comments
Link multiple accounts with the same email
2 votes · 0 comments
Support ordering by nested columns deeper than one level in .order()
3 votes · 0 comments
No comments yet.