Supabase Platform Access Control: Organization Permissions Breaking Changes on July 26, 2024

[w3b6x9]

These breaking changes are rolling out on July 26, 2024 and affects all organizations that have members assigned either the Developer or Read-Only roles.

All Supabase organizations invite users and assign them to one of the following roles as part of membership to an organization:

• Owner
• Administrator
• Developer
• Read-Only (available only on Team and Enterprise plans).

Depending on the role, members are authorized to access a specific set of the organization's resources, such as permission to create a new project or change the billing email.

We recently re-evaluated the access that the Developer and Read-Only roles have and decided to implement changes to restrict them on a couple of resources to improve your organizations' security.

On July 26, 2024, we will turn off certain access that the Developer and Read-Only roles currently have to your organization's resources. The following table is to illustrate the breaking changes that will be going into effect:

Resource	Action	Developer	Read-Only
Integrations1
Authorize GitHub	-	✅ → ❌	✅ → ❌
Add GitHub Repositories	-	✅ → ❌	✅ → ❌
GitHub Connections	Delete	✅ → ❌	❌2
Vercel Connections	Update	✅ → ❌	❌2
	Delete	✅ → ❌	❌2

You can learn more about our Platform Access Control here: https://supabase.com/docs/guides/platform/access-control.

If you have any questions or concerns please contact support.

Footnotes

1. Existing integrations will continue to work. ↩

2. Role's permission to the resource and action will remain the same. ↩ ↩² ↩³