Skip to main content
4-eyes review adds a second, independent sign-off before a resolution takes effect, a standard segregation-of-duties control for higher-risk investigations.

​
Setting it up

On the maker blueprint, set 4-eyes review to a checker blueprint. Setting this field is what turns 4-eyes on for the maker blueprint, there is no separate toggle.

​
How it works

  1. An officer on the maker blueprint resolves a case as usual (false positive or valid threat, plus a note if required).
  2. Instead of closing, the case status stays Open, the proposed resolution is staged, and the case moves into the checker blueprint’s queue. The case timeline logs Submitted for approval.
  3. A checker reviews the case’s Overview tab, where a dual-control banner shows Approve and Reject actions.
  4. Approve applies the staged resolution: the case becomes Resolved with the original resolution and note, credited to the officer who submitted it. The timeline logs Approval granted then Resolved.
  5. Reject clears the staged resolution and returns the case to the maker blueprint. The timeline logs Approval rejected, and the maker is notified.
The officer who submitted the resolution cannot approve or reject it themselves, enforced server-side. Attempting to do so returns a 403. (Approving or rejecting a case with no resolution pending approval returns a 409.)

​
Notes

  • The checker blueprint’s own assignment, escalation, and content settings apply while a case is in its queue, it is a real blueprint, not a special mode.
  • A case can only have one resolution staged at a time; requesting more information (Awaiting user) is blocked while a resolution is pending approval.
  • 4-eyes pairs with required resolution notes: turn both on for your highest-risk blueprints to require both a documented rationale and a second reviewer.