getsentry / getsentry/sentry

Organisation Settings - Restricting overriding of organisation/project settings

Open
#84,177 5 comments 0 reactions 0 assignees View on GitHub
Product Area: Settings - Members
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.