Advanced Policies: Multi-User Requests Bypass Preventive Control While Single-User Requests Are Blocked

During testing, I observed a difference in behavior between single-user and multi-user requests when Advanced Policies are configured.

For a single-user request, a policy violation is detected during submission, and the request is prevented from proceeding.

However, for a multi-user request, the request is submitted successfully, and the policy violations are generated afterward instead of blocking the submission.

Is this the expected behavior for Advanced Policies in multi-user request scenarios?
Alternatively, is there any recommended configuration or handling to enforce preventive controls consistently across both single-user and multi-user requests?

@sruthiPatlolla Yes. this is the expected behavior. for multiple users, it opens a policy violation work item to take action against each user.

I think you can handle this using a plugin that you can attach to the Submit button of request page. so when you click on submit, your plugin will be called and it will do the evaluation and will block/allow the submission as per your configuration.

Thanks for the confirmation, @Neelmadhav.
I appreciate the suggestion about using a plugin. We’ll look into that option.

yes go with plugin, that will be the correct approach to design your solution for this requirement.