1
Project Scoped Access for Teams plan
Source: supabase/supabase#40389 · opened by @jdragon3001
I really don't understand why project scoped access is exclusive to a tams plan, which we have to pay $599 a month for. This is far out of our budget and having project scoped access is essential to security that we need to set us up to be able to afford that higher plan. Why is this exclusive to teams--do I misunderstand the complexity of this adding this permission granularity?
<img width="587" height="458" alt="Screenshot 2025-11-12 111143" src=" />
<img width="587" height="458" alt="Screenshot 2025-11-12 111143" src=" />
No pledges yet. Be the first to back this.
Comments
Similar requests
Is project-scoped access control to dashboard ‘coming soon’ to Pro plan?
3 votes · 0 comments
Add a scoped, read-only metrics / monitoring API key (alternative to service_role)
7 votes · 0 comments
Scoped Auth via non-unique emails on auth.users
4 votes · 0 comments
URGENT – Pro plan not applied to active project, blocking access to support
1 vote · 0 comments
Team scoped access tokens for automation (eg: Terraform, GHA)
1 vote · 0 comments
No comments yet.