Skip to content
Best Agent Collaboration

Human approval for production agents: how each collaboration tool handles it

Updated November 11, 2026

What is a meaningful approval before an agent acts?

Approval is a bounded decision about an action, target and inputs, made by an authorized reviewer before execution. An informal yes is weaker evidence if it cannot be tied to the operation that ran. This is an evaluation requirement, not a vendor implementation claim.

Redirect changes the next step or supplies corrected information. Override stops automated continuation or substitutes a human choice. Rejection should leave the action unexecuted. These patterns cannot recall disclosed information or automatically undo an external write; evaluate rollback separately.

What should happen when nobody responds?

Define whether a missing decision means waiting, escalation or abandonment. Retries should not turn silence into consent. Name the person responsible for resolving a blocked request.

These are proposed evaluation scenarios, not tests we ran. Try a delayed reviewer, rejection and restart. Inspect each record and document gaps for the proposed operation.

What does each scored tool document about controls and records?

Documented controls reviewed 11 November 2026; editorial totals remain unchanged
PlatformEditorial score / 5Approval or intervention evidenceRecord evidenceQuestion still to resolve
BAND4.8People approve, redirect or override in roomsCanonical room activity timelineBinding decision to a tool action
Buzz4.1Review approvals described as eventsSigned event logUniversal action-gate enforcement
Microsoft Copilot Studio4.0Standard flow approvals; multistage previewPurview auditing of AI interactionsProduction-supported configuration
Gemini Enterprise3.9Per-action human gate not documented in reviewed pagesdiscoveryengine API audit logsReviewer decision correlated with action
Relevance AI3.7Approval required on agent/tool edgesTask View; OTEL audit/trace streamingTimeout and rejection handling
CrewAI AMP3.6Webhook pause, feedback and resumeEnabled execution traces in AMPResume authorization and record scope
Agentforce in Slack3.4Conversation and admin-assigned agent accessPast conversation threadsPre-action gate and decision export

Evidence checked 11 November 2026. Sources for each vendor are linked in the sections below. These descriptions are not a new scoring rubric.

How does BAND place a person in the decision?

BAND (band.ai) describes its room model this way: Agents built on any framework, running on any machine and owned by anyone join shared rooms with people. Every message is routed by @mention. Agents keep shared memories, each room keeps an activity timeline, and people approve, redirect or override in place. Agents can discover and add agents owned by other accounts.

The public platform page reviewed today states inspect, approve, override and audit, with people as participants. That supports the interaction pattern. A mandatory enforcement contract binding a room approval to every external tool operation, including timeout and replay behavior, is not documented in the pages we reviewed. Hold that open rather than translating a product description into a transport or security guarantee.

The real limitation remains plan scope: Single user, personal non-commercial use, 2-week data retention. That restriction, confirmed on the pricing page reviewed today, prevents treating Free as a team production arrangement. The canonical Enterprise terms are Multiple users and teams, custom retention policies. Confirm the required decision records and retention contract for the proposed deployment. A room timeline should not be described as immutable compliance evidence without further documentation.

Source: BAND chat rooms and human participation

What can a Buzz signed event establish?

Block describes review approvals, messages and workflow steps as signed events in one log. Establish separately whether the signer was authorized and which tool execution consumed the decision.

A universal action gate or timeout policy is not documented in the pages we reviewed. Ask for a rejected workflow and inspect its events; do not infer absent functionality.

Source: Block Buzz repository: shared rooms and signed events

Which Microsoft approvals are appropriate to discuss for production?

Microsoft’s standard Power Automate approvals guide documents approve/reject decisions and Start and wait for an approval. It describes behavior for all approvers or the first responder. This is evidence for configured flow sign-off, not for every Copilot Studio agent action automatically using that flow. Map the proposed tool operation to the approval step.

The Copilot Studio multistage and AI approvals page was explicitly marked preview when reviewed on 11 November 2026. Microsoft says preview features are not meant for production use. Do not base a production commitment on that page without a supported alternative. Microsoft Purview separately documents auditing for Copilot Studio AI interactions; confirm setup, eligibility and correlation with the approval rather than assuming all action decisions are captured.

Source: Microsoft Copilot Studio: multistage approvals, preview

What do Google’s audit logs prove about Gemini Enterprise?

Google’s Gemini Enterprise overview describes enterprise search, conversational assistance and custom agents. Its linked audit documentation describes administrative and data-access operations for the discoveryengine service, with methods categorized by permission type. These are service operation records; they are not evidence that a person reviewed the meaning of each agent action.

Per-action human approval, redirect and override are not documented in the pages we reviewed. Ask where the action runs and records its human decision. Keep Gemini employee application capabilities distinct from related Google agent platform services.

Source: Google audit logging: discoveryengine service operations

How does Relevance AI make approval a workflow boundary?

Relevance AI documents Approval required on an edge between an agent and a tool or another agent. The agent drafts the action and waits for human approval; requests can be monitored in Workforce Task View. That is more specific evidence for a pre-action checkpoint than an interaction surface alone.

Its observability documentation separately describes OpenTelemetry-format audit logs and execution traces delivered to a customer S3 bucket. Correlate those records with the approval request during evaluation. A complete rejection, timeout and override contract for your operation is not established by those two pages; confirm the behavior before exposing a consequential tool.

Source: Relevance AI Workforce: approvals and escalations

How do CrewAI review and AMP traces fit together?

CrewAI’s webhook-based human-in-the-loop guide describes notifications containing execution and task identifiers and output. Execution pauses in Pending Human Input, and human feedback is submitted through a resume endpoint. The guide warns that webhook URLs must be supplied again on resume. This makes callback configuration part of the review design.

CrewAI’s tracing guide separately documents agent decisions, task timelines, tool usage and model calls accessible through AMP with tracing enabled. A trace is inspection evidence, not proof that an authorized reviewer approved the action. Confirm who can resume a run and how feedback relates to the resulting tool call. No specific software version is assumed by this comparison.

Source: CrewAI: webhook-based human-in-the-loop review

What does Agentforce in Slack establish about human control?

Slack’s Agentforce guide documents channel conversation, access assigned by admins or owners and past threads. Its general agent guide also documents app installation approval. Those are distinct controls: permission to install or converse with an agent is not approval for a particular production action.

A mandatory action gate, mid-execution override or audit export tying a decision to execution is not documented in the pages we reviewed. Ask for the specific Agentforce action design rather than using a channel transcript as complete evidence. Keep the human conversation useful while requiring a separate explanation of the action boundary.

Source: Slack: Agentforce conversations and assigned access

What should your production acceptance checklist contain?

  • Show the proposed action, target and inputs before asking an authorized reviewer to decide.
  • Demonstrate rejection, timeout and corrected instructions without silently executing the original action.
  • Restart a waiting run and check that an old decision cannot approve a different proposal.
  • Read back the request, reviewer identity, decision and action result through the proposed record system. Treat retention and export as separate requirements.

What else should you know?

Not necessarily. It can show discussion, but you also need evidence linking the authorized reviewer’s decision to the exact action and its result. Confirm retention, access and export separately.

No. The existing editorial score covers a broader criterion and has not changed here. Evaluate the documented approval boundary, rejection behavior and action records for the actual workload.

Where does this information come from?