---
number: 29494
slug: 29494-supabase-platform-access-control-project-permissions-breaking-changes-on-october
published: 2024-09-24
discussion: https://github.com/orgs/supabase/discussions/29494
labels:
  - security
  - breaking-change
page: https://supabase.com/changelog/29494-supabase-platform-access-control-project-permissions-breaking-changes-on-october
---

# Supabase Platform Access Control: Project Permissions Breaking Changes on October 15, 2024

_These breaking changes are rolling out on October 15, 2024 and affects only organizations on the Enterprise plan that have implemented project permissions with members assigned the Developer role._

Supabase launched new granular access control for Enterprise organizations so that its members are given access to specific projects instead of the entire organization. You can check out our [Launch Week 12 announcement](https://supabase.com/blog/platform-access-control) to learn more.

We recently re-evaluated the access that the **Developer** role has and decided to implement changes to restrict them on a couple of resources to improve your project's security.

On October 15, 2024, we will turn off certain access that the Developer role currently has to your project's resources. The following table is to illustrate all of the breaking changes that will be going into effect:

| Resource                 | Action   | Developer    | Read-Only   |
| :------------------: | :------: | :----------: | :----------: |
| **API Configuration**     |          |              |              |
| JWT Secret   | Generate new   | ✅ → ❌       | ❌[^2]        |
| API Settings  | Update  | ✅ → ❌       | ❌[^2]        |
| **Auth Configuration**     |          |              |              |
| Auth Settings   | Update   | ✅ → ❌       | ❌[^2]        |
| Advanced Settings   | Update   | ✅ → ❌      | ❌[^2]       |
| **Storage Configuration**     |          |              |              |
| Upload Limit   | Update   | ✅ → ❌       | ❌[^2]        |
| S3 access keys  | Create   | ✅ → ❌       | ❌[^2]        |
|                             | Delete   | ✅ → ❌       | ❌[^2]        |
| **Edge Functions Configuration**     |          |              |              |
| Secrets  | Create   | ✅ → ❌       | ❌[^2]        |
|                             | Delete   | ✅ → ❌       | ❌[^2]        |
| **Authentication**     |          |              |              |
| Providers  | Update   | ✅ → ❌       | ❌[^2]        |
| Rate Limits  | Update   | ✅ → ❌       | ❌[^2]        |
| Email Templates  | Update   | ✅ → ❌       | ❌[^2]        |
| URL Configuration  | Update   | ✅ → ❌       | ❌[^2]        |
| **Logs & Analytics**     |          |              |              |
| Events Collections  | Create   | ✅ → ❌       | ❌[^2]        |
|   | Update   | ✅ → ❌       | ❌[^2]        |
|   | Delete   | ✅ → ❌       | ❌[^2]        |
| Warehouse Access Tokens  | Create   | ✅ → ❌       | ❌[^2]        |
|   | Revoke   | ✅ → ❌       | ❌[^2]        |

[^1]: Existing integrations will continue to work.
[^2]: Role's permission to the resource and action will remain the same.

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](https://supabase.help).