A county requires human approval before any SOAR step that disables Entra accounts for judges. What playbook design control is that?

A county that requires human approval before any SOAR step that disables Entra accounts for judges is placing approval gates before high-impact civic account actions. Judicial accounts affect court calendars, sealed matters, and continuity of justice; placing approval emails in SOAR playbooks before high-impact civic account actions only sends a notification without blocking execution, so it does not prevent premature disablement of judge accounts. An approval gate preserves enrichment and notification speed while ensuring a human validates context before identity disablement.

Why the other options fail by concept: Placing approval emails in SOAR playbooks before high-impact civic account actions fails to enforce control—an email is a notification, not a blocking gate, so the playbook can still disable the judicial account without a human validating context before court disruption occurs. Placing approval gates in SOAR playbooks before high-impact civic account reviews gates the wrong action—a review is read-only visibility, so it delays context gathering while leaving the high-impact disable step for judges ungated and unprotected. Placing approval gates in SOAR workbooks before high-impact civic account actions puts the control in the wrong object—workbooks are for visualization and analysis, not automated enforcement, so it cannot block the playbook from executing the premature judicial disable.

Exam caveat: Approval gates add latency; they should be reserved for high-impact actions, with clear SLAs so approvers do not become an unmonitored bottleneck during real incidents. Operational check: mark judicial and other high-impact disable steps as gated, page the designated approver with case context, log the decision, and keep ungated enrichment steps running while waiting.