Enforce the engagement object permission on the questionnaire answer view - #15666
Open
svader0 wants to merge 1 commit into
Open
Enforce the engagement object permission on the questionnaire answer view#15666svader0 wants to merge 1 commit into
svader0 wants to merge 1 commit into
Conversation
…view Align answer_questionnaire with the other engagement-scoped questionnaire views by always applying the object-level edit check. Adds a regression test.
Maffooch
requested changes
Aug 14, 2026
Maffooch
left a comment
Maffooch
left a comment
Contributor
There was a problem hiding this comment.
It is a feature to allow surveys to be answered without a login if configured to be available
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
2 participants
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.
Hardening / consistency improvement to the engagement-scoped questionnaire views. Aligns the answer view with its siblings so it always applies the object-level edit permission check, and adds a regression test. No functional change for correctly-permissioned users.