1
Request for more granular project permissions
Source: supabase/supabase#43042 · opened by @MarcMadeIt
Hi Supabase team đź‘‹
We’re currently missing more granular access control within organizations.
Today, if someone needs permission to modify a single project, they must be made Admin, which gives them access to modify all projects in the organization. That’s not ideal for agencies or teams managing multiple client projects.
It would be great to introduce project-specific roles, so a user could:
• Be able to edit one project
• Have limited or no access to others
This would improve security and make multi-project organizations much easier to manage.
Thanks for building such a great platform 🙌
Marc
A lot of space to new features :)
<img width="599" height="1187" alt="Skærmbillede 2026-02-20 kl 11 32 25" src=" />
We’re currently missing more granular access control within organizations.
Today, if someone needs permission to modify a single project, they must be made Admin, which gives them access to modify all projects in the organization. That’s not ideal for agencies or teams managing multiple client projects.
It would be great to introduce project-specific roles, so a user could:
• Be able to edit one project
• Have limited or no access to others
This would improve security and make multi-project organizations much easier to manage.
Thanks for building such a great platform 🙌
Marc
A lot of space to new features :)
<img width="599" height="1187" alt="Skærmbillede 2026-02-20 kl 11 32 25" src=" />
No pledges yet. Be the first to back this.
Comments
Similar requests
PAT security vulnerability for MCP - prod access
2 votes · 0 comments
Supabase urgently needs per project permissions
11 votes · 0 comments
Separate Point Queries and Listing for Permissions
1 vote · 0 comments
Missing features for using management API in CI
1 vote · 0 comments
Feature Request: Add a “Billing” Role to Team Member Permissions
1 vote · 0 comments
No comments yet.