Organisation Settings - Restricting overriding of organisation/project settings

[Angelodaniel]

Problem Statement

Restricting access to sensitive settings: For example, allowing only specific roles to update project rate limits. This ensures critical configurations are protected and minimizes accidental changes by unauthorized users.

Configuring permissions for API interactions: Restrict project settings modifications through the API to prevent overrides made by unauthorized teams, even when using Terraform.

Use Case:
Organizations that are primarily using Terraform for Sentry configuration. However, teams can override these settings via the API. Adding RBAC would allow fine-grained permissions to control who can make such changes, ensuring a secure and governed setup.

Solution Brainstorm

No response

Product Area

Settings - General

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-settings-members for triage ⏲️

[leedongwei]

We have Team Admin and Team Member role. The member role cannot modify settings.

Are you looking for more layers of team roles? How would that look like?