Skip to content

Approve or deny held calls

This content is not available in your language yet.

When a rule says a call needs a person, Guard holds it. This guide shows what you see and what each choice does, and how to say who may approve.

Run geo guard reviews. It lists the calls waiting for a person. If nothing is held, it says so.

Each held call shows:

  • what exactly was asked, as a list of arguments;
  • which rule held it, which version of your rules that is and how long ago your rules were last updated;
  • when the request runs out, and who it is waiting for (a request passed on because nobody answered in time says so);
  • what Guard knows from its own record, such as earlier calls for the same request, and what it cannot see.

Read the arguments. Approving lets that exact call through once. Any change to it needs a new approval.

Only people named as approvers can approve, for the tools and amounts their role covers.

Take the identifier from geo guard reviews.

What you can do with a held call

Command What it does
geo guard approve <id> The exact call goes through, once. The agent can retry that exact call.
geo guard deny <id> Refuses the call. Guard’s approval request has no place for a reason, so the agent does not receive one, and a retrying agent is only held again.
geo guard revoke <id> Takes back an approval that has not been used yet.

Add an approver for one tool, with an optional limit on the amount. Guard prints the person’s credential once. Give it to them. It is not kept on your computer.

geo guard approver-add <name> --tool <tool> --max-amount 100
geo guard approvers
geo guard approver-remove <name>

Removing someone stops their credentials, and their earlier approvals are not used. A request goes first to the role with the lowest limit that covers it, then on to the next if nobody answers in time. Guard’s own admin access never approves.

Let specific calls skip one rule for a while

Section titled “Let specific calls skip one rule for a while”

An approver can grant an exception, for example for one order’s refund up to an amount, for at most seven days. geo guard exception-revoke ends one at any time.

geo guard exception-grant --tool payments --rule <rule> \
--match order_id=1234 --max-amount 200 --hours 24 --reason "Customer escalation"
geo guard exception-revoke <id>

At least one --match field=value is required. An exception never skips the refund-once check, spending limits, a stop or a changed tool. Each one names who granted it and why.

Run geo guard kill to stop all new calls, or geo guard agent-stop <agent> to stop one agent. Both stop new calls only. Anything already sent is not undone. See Guard.