Approval gates

Approvals keep sensitive, externally visible or policy-controlled actions under human review. The Workflows Console exposes an approval queue in Work → Approvals and individual solutions can also present approval requests in their own context.

What an approval means

An approval request represents work that is ready for a permitted reviewer to evaluate. It does not mean the requested action has already happened. Reviewers should inspect the proposed result and its context before deciding.

Approval records can originate from more than one execution surface, including hosted workflows and Hermes deployments. The runtime contract requires writes, publishing and external distribution to keep their approval gates regardless of whether work executes in Cloud or Hermes.

Reviewer responsibilities

• Confirm the request belongs to the expected Workflows organization.
• Review the proposed action and any attached result or artifact.
• Check that the assistant used the expected knowledge and approved systems.
• Reject or request correction when context is missing or the output is unsafe.
• Treat approval history as operational evidence; do not bypass it through a direct provider action.

Exact approval actions and role requirements vary by solution. Follow the labels and access rules shown in the Workflows Console.

Next: Knowledge.