11
Supabase urgently needs per project permissions
Source: supabase/supabase#20942 · opened by @bombillazo
Hey, we are having an unforeseen bad development and operational experience due to how permissions are global across projects in an organization. We cannot (and _should_ not) give access to developers, agents, and operations team to our production environment. Still, they require access to other testing, staging, and administrative projects we run on Supabase. We are having a lousy time juggling permissions and limiting access to the projects.
This is not an uncommon scenario. I also imagine having an organization serving multiple clients with different projects but having trouble inviting client users to the dashboard since that opens up the projects of other clients.
Is there any expectation that this behavior will change? It will significantly improve our experience of using the Supabase platform.
This is not an uncommon scenario. I also imagine having an organization serving multiple clients with different projects but having trouble inviting client users to the dashboard since that opens up the projects of other clients.
Is there any expectation that this behavior will change? It will significantly improve our experience of using the Supabase platform.
No pledges yet. Be the first to back this.
Comments
Similar requests
URGENT – Pro plan not applied to active project, blocking access to support
1 vote · 0 comments
Request to Enable External JWT Authentication with Firebase (Project: dropnow-2025)
1 vote · 0 comments
Missing features for using management API in CI
1 vote · 0 comments
an way to reset/rollback project database to the first version
11 votes · 0 comments
Configure External PostgreSQL for Supabase Instead of supabase-db
3 votes · 0 comments
No comments yet.