Human Approvals

Keep work moving.
Bring in a person when it matters.

Let policies hold a consequential action for review and give the decision-maker readable context about the agent, destination, resource, risk, and reason. Approve or deny the request and keep the result in the history.

How it works

A review request should explain the decision, not just ask for a click.

When a policy requires approval, Iron Gorilla can pause the action and show why it was held, what destination and resource are involved, which business fields matter, and what the workflow has already done. Sensitive values are redacted in the review presentation.

Product Walkthrough

Follow one request from queue to recorded decision.

See how a reviewer understands a held action, checks the supporting context, makes a decision, and returns to the completed record later.

Review at the right moment

Hold only the work that a policy routes to a person instead of treating every action the same.

Context before the choice

Bring the destination, resource, action, workflow, validation, and relevant redacted fields into one review.

A decision that stays traceable

Keep approved, denied, and expired requests connected to the reviewer and downstream run.

Why it matters

What this changes once the work gets real.

Policies decide when to ask

Approval appears when a configured rule gates the action; it is not assumed for every task.

A person keeps the final choice

The request can provide context and recommended next steps while the reviewer chooses whether work continues.

History closes the loop

Review the decision, comment, recorded effects, and linked run after the request leaves the pending queue.

Put human judgment where the work needs it most.

Give reviewers enough context to decide and keep that decision attached to the work.