getsentry / getsentry/sentry

Ability to assign a user to a read-only role

Open
#120,848 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Product Area: Settings - Members Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

I'd like to have the ability to assign some of my users to a read-only role. Ideally they would be able to query events, releases, etc, but they would not be able to take actions that update data models like resolving an issue or finalizing a release.

Solution Brainstorm

My team came across this while writing a few scripts to do some actions through the Sentry API. Specifically we were considering including an action to mark an issue as resolved through a slack bot interaction, but after some discussion we think that we don't want to give that ability to everyone, since they might not fully understand the result of that in Sentry.

Our scripts currently allow you to bring your own token and we realize that we could change that to only use an existing token from our tool (with only event:read access), but we think that a cleaner option would be to have a standard role with that type of permission.

Product Area

Settings - Members

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Settings - Members area and trace how the existing event:read token permission is represented and assigned to users. Compare the permissions needed for querying events and releases with actions such as resolving issues or finalizing releases; done means a standard read-only role can perform the former while being blocked from the latter.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.