getsentry / getsentry/sentry

Make team contributors unable to edit code mappings

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

Description

### Problem Statement

It looks like currently, team contributors are able to edit the code mappings of source code management integrations. Here is a reproduction from my test user and org:
https://github.com/user-attachments/assets/c509d4e3-6422-4de7-980c-5631a568e1be

Note that while it is possible to add/edit code mappings, only Owners, Managers, and Admins can delete them.

### Solution Brainstorm

This can be considered a security risk by some customers, especially since such edits are not shown in the audit logs either. It should be possible to add/edit code mappings only by Team Admins and above.

### Product Area

Settings - Members

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start in the Settings - Members code-mapping permission flow and reproduce the behavior with a team contributor account. Done means team contributors cannot add or edit code mappings, while Team Admins and higher roles retain that ability.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.