grafana / oncall

Developer-friendly incident response with brilliant Slack integration
GNU Affero General Public License v3.0
3.51k stars 288 forks source link

Prohibit editor to delete, modify settings and create swaps and overrides in schedules of other teams. #4234

Open omalko394 opened 7 months ago

omalko394 commented 7 months ago

What would you like to see!

Hello! We are currently using an OSS setup of Grafana with Grafana OnCall integrated. One of our teams, which is included in the escalation chains for all other teams, faces an issue where team members are unable to view and access to alerts that belong to other teams. To address this, we attempted to modify the Teams and Access Settings to allow all users to see team names and access team resources. However, this led to an unintended consequence where every user with editor rights (all our users had such role to be able to manipulate with alerts) gained the ability to delete, modify settings, and create or modify swaps and overrides in the schedules of other teams. Is it possible to prohibit editor role to delete, modify settings and create swaps and overrides in schedules of other teams?

Product Area

Auth, Schedules

Anything else to add?

Grafana OSS 9.5.7 Grafana OnCall OSS 1.3.117

Steps to Reproduce:

github-actions[bot] commented 7 months ago

The current version of Grafana OnCall, at the time this issue was opened, is v1.4.0. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you :smile:!