SECURITY · GOVERNANCE & HITL

Autonomy without control is a liability. ABX gives you both.

The governance model is not a safety feature bolted on after the fact. It is the architecture. Every execution in ABX is designed around the moment human control is required — and only that moment.

GOVERNANCE

One question governs every execution

THE GOVERNANCE QUESTION

"Does this action leave the user's own workspace and touch another person?"

LOGIC 1 – AUTONOMOUS

No approval required

Pull data from connected systems
Analyse and synthesise
Generate reports to user only
Enrich data locally
Draft content to workspace

LOGIC 2 – APPROVAL REQUIRED

Always stops for sign-off

Send emails or messages
Update CRM records
Book calendar events
Publish or post externally
Share or distribute documents

What approval looks like in practice

ABX presents the proposed action clearly before executing. What will be sent. To whom. From which system. With what content. You review, approve, edit, or reject.

ABX NEEDS APPROVAL

"25 personalised emails are staged and ready. Review each one, then approve to send — or decline and the system will adjust. Approve all · Review individually · Edit before sending · Decline"

Pro: configurable governance

Pro customers can define custom approval thresholds, multi-person approval chains, and workflow-level governance rules. ABX enforces them automatically on every execution — no manual oversight required.

PRO GOVERNANCE FEATURES

Custom approval thresholds per execution type · Multi-person approval chains (e.g. two approvers required for CRM writes) · Workflow-level rules (e.g. all email batches above 50 require senior approval) · All rules stored, versioned, and auditable

See the full security architecture

Trust Center · Audit log · DPA request