Module: Control · Approvals
Approval Before a Control Runs
A Control Moderator can require that runs of a control are approved before they start, by naming an approval workflow on it. Every check happens first, so an approver is never asked about a run that could not happen, and the approval names the control, its exact version and its risk, so an approver without any Control role can tell what they are signing off. A scheduled or event-triggered control is approved once per script version and set of values; any change asks again.
- 01
Pain Point
What's the problem?
A script that changes the tenant should not run on one person's say-so, but getting a second signature usually means an email thread.
- 02
Remedy
How do we attack it?
Name an approval workflow on a control, so its runs wait for an approver before they start
- 03
Your Value
What do you get out of it?
Changes to the tenant carry a second signature without leaving the platform