TaskGate Docs
taskgate.ai Request access
Control

Approvals

When policy requires approval, the action waits in the Approvals inbox until the right people decide. The approver sees the exact action that will run.

Who is asked

The rule that requires approval names its reviewers. A reviewer group can be made of:

A group can require more than one approver, and groups can be ordered so one signs off before the next. The people behind a request — whoever asked for it, the person the agent acts for and whoever started the run — are kept out of its reviewers.

The inbox

The inbox lists what is waiting on you. When nothing is, it reads Nothing is waiting on you. Open a request to see the full action, the rules that matched and how it got here.

ButtonWhat it does
ApproveApproves the action. When the action carries an amount, the button shows it, for example Approve €4,200.00.
Request changesSends the action back for changes.
Ask for infoAsks for more information. Once it is answered, the request is waiting again.
RefuseRefuses the action. It never runs.
ConfirmShown instead of the buttons above when the request is a confirmation.

A rationale is required to refuse. For an action that cannot be undone, a rationale is required to approve as well.

After approval

An approval is used once, for the action it was given for. It is valid for a limited time — one hour unless the rule sets otherwise. When the action executes, policy is checked again: if the approval no longer meets the policy, a new approval is requested and the action does not run on the old one.

When someone is away

Slack and Microsoft Teams

Approval requests can reach reviewers in Slack or Microsoft Teams, where they can acknowledge or claim a request. The decision itself is made in the TaskGate console.