1
Branching Access Control
Source: supabase/supabase#43106 · opened by @johnBrereton
Supabase branching is a great workflow feature, but the current access control model makes it difficult to use in real production environments. Permissions are only managed at the project level, which means any engineer who needs to work on a branch must also be given access to production. In most teams, this isn’t acceptable because not all developers, contractors, or junior engineers should have visibility into or the ability to modify prod resources.
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature Request: Add Bitbucket Support for Supabase Branching
5 votes · 0 comments
Branching - workflow/git provider options
9 votes · 0 comments
Persistent staging/prod project parity — schema + edge functions + auth sync without ephemeral branching
1 vote · 0 comments
[RFC] Query builder immutability and safe branching semantics across Supabase SDKs
1 vote · 0 comments
Branching - Add `--with-data` option to GitHub integration
1 vote · 0 comments
No comments yet.