---
number: 35172
slug: 35172-project-scoped-roles-now-available-in-team-plans
published: 2025-04-21
discussion: https://github.com/orgs/supabase/discussions/35172
labels:
  - security
page: https://supabase.com/changelog/35172-project-scoped-roles-now-available-in-team-plans
---

# Project scoped roles now available in Team plans

[Project scoped roles](https://supabase.com/docs/guides/platform/access-control#organization-scoped-roles-vs-project-scoped-roles) are now available for all Supabase Team plans.

With project scoped roles, you can:
- Restrict team member access to specific projects
- Set different permission levels for different projects
- Maintain better security boundaries within your organization
- Simplify compliance requirements, including HIPAA

Each member in the organization can be assigned a role scoped to the organization or to specific projects. If the member has a role at the organization level, they will have the equivalent permissions for that role across all current and future projects in the organization.

![image](https://github.com/user-attachments/assets/a0d0ed5e-2e17-44a9-8eed-6f89d78f6482)

With project scoped permissions, you can assign members to roles scoped to specific projects within your organization.

![image-2](https://github.com/user-attachments/assets/11f8c18c-44b8-44aa-adfd-ddc6c5b73baf)

To get started with project scoped roles visit your organization's [team settings page](https://supabase.com/dashboard/org/_/team) to add users and manage their roles. If you're adding project scoped roles for a new user, you can only select one project when sending the invite. You can assign roles to multiple projects after the user accepts the invite.