A review step lets a person decide before the mission makes the next consequential change. This is separate from the upstream paid control that approves publishing a workflow.

​
Prepare a review packet

Include the item identifier, requested decision, relevant evidence and the rule that needs attention. For a bill, show the supplier, amount, required documents and any exceptions. Use the human-input or approval gadget available in your deployment, or route the decision through the customer’s existing system. Configure the action from its actual supported inputs rather than assuming every approval option exists in Community.

​
Confirm who may decide

A link in an email or a public webhook is not proof of a person’s identity. Your chosen review surface must enforce the approver identity and authority required by the business rule.

​
Define the outcomes

Choose what happens on approval, rejection, expiry and no response. Record the decision, item/version, approver identity and time in the system that owns the business evidence. A changed bill should not silently reuse a decision for an earlier version.

​
Test the wait and resume

  1. Start a sample item requiring review.
  2. Confirm the mission pauses at the intended step.
  3. Submit an authorized test decision.
  4. Confirm it follows the correct path once.
  5. Test an expired, repeated or unauthorized response.
Paused runs remain subject to retention and pause limits. Decide how to escalate items that approach their expiry.