Repository navigation
feat(service-accounts): Require service_account:read for service account reads - #129497
Merged
Merged
Conversation
…unt reads List and detail now require service_account:read instead of org:read. Manager and Owner hold the new scope, so members can no longer list service accounts. The scope is explicit: org:read and service_account:write do not grant reads, so tokens that read and write need both service account scopes. Co-Authored-By: Shaun Kaasten <shaun.kaasten@sentry.io>
github-actions
Bot
added
the
Scope: Backend
Members should be able to list service accounts, for example to pick one for a Seer automation. Member and Admin now hold service_account:read, so moving reads off org:read keeps their access. Writes stay limited to Manager and Owner. Co-Authored-By: Shaun Kaasten <shaun.kaasten@sentry.io>
gricha
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Service account list and detail reads now require
service_account:read. Member, Admin, Manager, and Owner receive the scope, preserving their access; write permissions are unchanged.via shaun.kaasten.
--
View Session [Sentry]