Approval gates

AI that asks before it acts.

Sensitive, financial, legal or external actions pause for a human yes before anything happens.

Workspace
Approval request
APPROVAL GATE

Vendor outreach is blocked

Finance and Legal must approve the packet before any external message can be sent.

People stay in charge of the moments that matter.

Nothing risky runs unseen

You choose which actions need a review, so sensitive steps always stop for a person first.

Approve where you already work

Review requests in the workspace, or from Slack and Microsoft Teams, with the full context attached.

Trust grows over time

Start strict. Loosen rules as an agent proves itself on real work, and tighten them again whenever you need to.

Set rules by action and risk

Decide which actions need approval before an agent ever runs. Gate external messages, payments above a threshold, contract changes or anything that touches a customer, and let routine steps carry on.

  • Rules by action, system or amount
  • Different rules for each team and agent
  • A named approver for every rule
Human review gate Approval request
Live
Approval required

Send renewal recommendation to vendor owner

Includes business context, evidence, risk flags, and action history.

Customer-impactingExternal communicationFinancial threshold
Approve Edit Escalate

Review with full context

An approval request shows the draft, the sources the agent used and exactly what will change. The reviewer can approve it, edit it, reject it or send it back with a note.

  • The draft and its sources side by side
  • The exact change before it happens
  • A note back to the agent when needed
Workspace
Northstar BI Renewal Owner Brief
Marcus Lee

Northstar BI sent a 12% renewal uplift. Keep Finance, Procurement, and Legal in one thread.

Renewal Research Agent

Owner brief is ready. Approval is required before vendor outreach.

Medium risk 7 events logged

Every decision is recorded

Each approval, edit and rejection is saved with who decided, when and why. The record sits next to the work it describes, ready for review or audit.

Audit and policy Governance console
Live
Controls RBACSkill accessModel policyApproval rules
Audit log

User approved packet

Agent called CRM tool

Knowledge source checked

How it works

From request to recorded result.

  1. The agent prepares the work

    It drafts the message, update or payment and gathers the sources behind it.

  2. The gate checks the rule

    If the action matches an approval rule, the run pauses before anything changes.

  3. A reviewer decides

    The right person approves, edits or rejects, with the full context in front of them.

  4. The action runs

    Only approved work goes ahead, exactly as it was approved.

  5. A receipt is saved

    The decision, the reviewer and the outcome join the run record.

Every feature runs inside the same six controls.

Identity, access, approvals, supervision, audit and policy apply to every agent and every run, whichever part of the workspace it happens in.

See governance and audit
  • Identity
  • Access
  • Approvals
  • Supervision
  • Audit
  • Policy
FAQ

Approval gates: questions and answers

Short answers to what teams ask before they put this part of SoftworkerAI to work.

Contact us directly
Which actions can need approval?

Any action you choose. Teams usually start with external messages, payments, contract changes, updates to customer records and anything above a spending threshold. Rules can be set by action, system, amount or team.

Who can approve an action?

The people you name for each rule. An approval goes to a designated person or role, such as a finance lead for payments or legal for contract changes, and only they can release the action.

What happens if no one responds?

The action stays paused, because nothing runs without a decision. The agent sends follow up reminders to the approver and can alert an admin when a step has been waiting too long.

Can we approve from Slack or Microsoft Teams?

Yes. Approval requests appear in the workspace thread and can also reach the channels your team already uses, such as Slack and Microsoft Teams, with the context attached.

Can approval rules be different for each team?

Yes. Each team can have its own rules and approvers. Finance can gate payments while support gates customer replies, all under one governance model.

Is every approval decision logged?

Yes. Every approval, edit and rejection is saved with the reviewer, the time and any note, as part of the audit trail for that run.

The multiplayer workspace for humans and AI agents is how teams move beyond prompting and safely hand AI real work. It gives people one place to plan, approve, and oversee execution, so they can run work with AI agents they can govern and trust.
The SoftworkerAI Team