Project-level "Debug Files Access" override ineffective when org-level "Debug Files Access" is more restrictive
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Setting "Debug Files Access" to a less restrictive role at the project level has no effect. The org-level restriction always takes precedence despite the project-level setting claiming to override it.
Confirmed combinations:
- Org:
Owner/ Project:Manager→ Manager accounts cannot download debug files - Org:
Manager/ Project:Member→ Member accounts cannot download debug files
- Set org-level Attachments Access to, for example,
ManagerorAdmin:
- Navigate to a project's settings (
Settings > <project> > Project Settings)
-
Under Membership, set Debug Files Access to
Member -
Log in as a user with the Member role
-
Attempt to download a debug file (e.g., source map or proguard mapping) from the project
Expected Result
The project-level setting overrides the org-level setting. Member accounts can download debug files for the project where the override is configured.
Actual Result
Member accounts cannot download debug files. The org-level Manager restriction appears to remain in effect despite the project-level override.
Product Area
Unknown
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the organization- and project-level Debug Files Access checks used when downloading source maps or ProGuard mappings. Reproduce the Owner/Manager and Manager/Member combinations from the issue, then verify that a project-level setting can override the organization restriction for that project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100