Give every teammate and agent the right level of access to your Workers

Cloudflare’s Developer Platform now supports granular access controls for Workers, allowing teams to assign precise permissions to teammates or agents. Previously, broad roles risked granting excessive access, potentially enabling unintended changes in production. The new system lets administrators restrict access to a single Worker, ensuring users can only interact with designated applications. This change addresses concerns about agents or team members making unauthorized modifications due to overprivileged access.

Four new roles have been introduced to define what actions users or agents can perform on a Worker. These include Metadata Read-Only for viewing settings and observability data without accessing code, Content Read-Only for reviewing source code without modifications, Editor for deploying changes without deletion rights, and Admin for full control over a specific Worker. Each role can be assigned to a user or an API token, ensuring access is scoped to a single application.

The roles are designed to balance security and usability, avoiding overly broad permissions that undermine least-privilege principles. Cloudflare plans to extend these scoped roles to other Developer Platform products, including D1, R2, and KV, maintaining consistent access controls across services. For example, Metadata Read-Only will allow debugging of a D1 database’s settings without exposing stored data, while Content Read-Only will enable code review without deployment capabilities.

In practical terms, these roles enable safer collaboration and automation. A CI/CD workflow can deploy changes to a single Worker without risking deletion or access to other applications. Similarly, a teammate debugging an issue can inspect metrics and logs for a specific Worker without viewing its code. The system ensures that even if a token is compromised, its impact remains limited to the designated Worker.