The latest updates on your projects. Learn more about Vercel for Git ↗︎

No changes detected in supabase directory.
This pull request has been ignored for the connected project xguihxuzqibwxjnimxev due to its connection settings.
Go to Project Integrations Settings ↗︎ in order to change this behavior.

Branching Preview Branches by Supabase.
Learn more about Supabase for Git ↗︎.

Docs site needs to be updated with new permissions matrix for project level roles

Just a nit - i'm wondering if we can save these permissions into the shared-types repo actually, cause the dashboard also has a UI showcasing all the perms - will be ideal to have one source of truth and dashboard can then render the perms based on that instead if hard coding

cc @inian i think the matrices here are all okay with explaining the permissions for org level functionality and project level functionality

but should we add another section to explain assigning roles on the organization vs assign roles on projects? (and also explain that project roles are available as part of the enterprise plan)

what i have in mind is like talking about

• If a user is assigned a role on the organization, the user will also have the equivalent permissions for that role across all projects under the organization (Refer to "Project permissions across roles" table)
• If you're looking to only allow access to specific projects for a user, then reach out to success to chat about enterprise or something

I came to this PR to check the upcoming docs for project granular role assignment, and it's not clear reading this. I quickly read it a few times and I nearly commented saying we haven't even mentioned it; however, it the opening lines do tease you that it might be possible.

Shouldn't we have a section with it's own header explaining you can assign roles per project vs org?

edit - noticed @joshenlim said the same thing above

Shouldn't we have a section with it's own header explaining you can assign roles per project vs org?

@MildTomato yes that's the missing piece and that's been passed back to Joshen and Hieu.

but should we add another section to explain assigning roles on the organization vs assign roles on projects? (and also explain that project roles are available as part of the enterprise plan)

what i have in mind is like talking about

• If a user is assigned a role on the organization, the user will also have the equivalent permissions for that role across all projects under the organization (Refer to "Project permissions across roles" table)
• If you're looking to only allow access to specific projects for a user, then reach out to success to chat about enterprise or something

@joshenlim yes this is the missing piece to the docs that need to be added. what you had in mind sounds great. can we also add in the piece that's like if a member has a project-level role then they no longer have a role at the org-level. that was unclear to me when looking at the project.