Skip to content

fix(notification-actions): Better access control for org-wide actions#113718

Merged
malwilley merged 1 commit intomasterfrom
malwilley/istanbul-v1
Apr 22, 2026
Merged

fix(notification-actions): Better access control for org-wide actions#113718
malwilley merged 1 commit intomasterfrom
malwilley/istanbul-v1

Conversation

@malwilley
Copy link
Copy Markdown
Member

Closes ISWF-2503

Tightens up the access control for actions not scoped to a particular project.

@malwilley malwilley requested a review from a team April 22, 2026 18:50
@malwilley malwilley requested review from a team as code owners April 22, 2026 18:50
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 22, 2026
Copy link
Copy Markdown
Contributor

@saponifi3d saponifi3d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm - just the question about if this should support org:write & alerts:write

# If the action has no projects, skip the project access check
# Notification actions not scoped to a particular project require org-level write access for mutations.
if not action_projects:
if request.method != "GET" and not request.access.has_scope("org:write"):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 should we also check for the alerts:write scope here? that's meant to allow users to have access to these permissions separately from the org scopes; but not sure if we want to enforce that on actions as well?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit confusing, but these notification actions are not related to workflow engine at all. These models are used for spike protection notifications

@malwilley malwilley merged commit b9ea4f8 into master Apr 22, 2026
57 checks passed
@malwilley malwilley deleted the malwilley/istanbul-v1 branch April 22, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants