Agent Studio / Governance / Approval Flows
← Home
Studio Guide

Governance

Approval Flows

Approval Flows is where people review the requests that agents and workflows send for human approval. When a request arrives, the run pauses until the reviewer approves it. Open it from Governance → Approval Flows in the left menu.

1.Where requests come from

A request is sent to Approval Flows when a run reaches a Human Approval block in a workflow, or when an agent wants to use a tool that you set to require approval.

  • Each request goes to one reviewer: the admin who built the workflow.
  • Reviewers aren’t notified by email. They see pending requests in Approval Flows, and builders also see them under Approvals in the Builder toolbar.
  • Requests don’t time out. Until a request is approved, the run doesn’t move forward.

Approval Flows is for approving actions while an agent runs. The sign-off a High-risk agent needs before it can be deployed is recorded separately, in Responsible AI.

2.The request list

Approval Flows lists every approval request, both the ones waiting for a decision and the ones already decided, so you can also follow up on requests your workflows sent and see whether they were approved or rejected.

  • Use the tabs to see Pending, Approved or Rejected requests, or All of them.
  • Each row shows the approval step that sent the request (such as Human Approval), the workflow it came from, its status, and when it was created.
  • Open a pending request to review it.

3.Review a request

Open a pending request from the list to review it.

The request page shows:

  • The approval step, the workflow it came from, when it was created, and its status, such as Pending
  • What the reviewer is asked to check, taken from the Human Approval block’s What to review setting (“Approval needed” if the builder left it blank)
  • Content pending approval: The content the run will continue with, such as an email draft or meeting notes

To decide:

  1. Read the content. If it needs a change, edit it directly in the Content pending approval box. The edited version is what continues through the run.

  2. Optionally, add a Decision note explaining why you approved or rejected the request, for the record.

  3. Select Approve to let the run continue, or Reject to stop it.

When you reject a request, give a reason the builder can act on, such as “Doesn’t have enough credentials to access the data.”

After a decision, the request shows its new status and a Decision section with when it was decided and the note. Select Back to queue to return to the list.

4.Where to add approvals

Add an approval before any action that is hard to undo. Good places are:

  • Before Send Email, Outlook Mail or Gmail sends a message an AI wrote
  • Before a Database Query, SharePoint or Google Sheets step changes data
  • Before an agent calls a tool that spends money or deletes something

In a workflow, place a Human Approval block right before the risky step and fill in its Title and What to review, so the reviewer knows what to check. For an agent’s tool, turn on approval when you add the tool.

Approval Flows — Studio DocumentationAgent Studio