AXME
Run approval workflows that span teams, departments, and external organizations
Enterprise workflows regularly need approvals from multiple departments or external partners — legal, finance, procurement, vendors. Each boundary is currently a manual handoff or bespoke API integration.
AXME Cloud's multi-tenant intent model supports approval chains that cross organizational boundaries — separate namespaces, isolated credentials, shared lifecycle visibility.
Enterprise workflows need approvals from legal, finance, procurement, or external vendors. Each boundary is a manual handoff or bespoke API integration.
Approvals that cross company boundaries
Procurement, legal, finance, and external vendors each need a gate in enterprise workflows. Email chains and shared spreadsheets do not scale; bespoke B2B portals take quarters to build.
AXME durable HITL with multi-tenant namespaces models each org as a participant on the same intent — audit visible on both sides of the boundary.
Example: vendor contract agent
Your agent drafts a vendor agreement; legal (your org) reviews; vendor counsel (external tenant) approves; finance signs budget. Each wait is WAITING_FOR_HUMAN with namespace isolation — vendor cannot see unrelated intents.
Export provides both parties evidence for their records.
SOLUTION
How teams solve this with AXME.
Legal review
Cross-org gate.
Finance sign-off
Budget approval.
Vendor approval
External partner.
Procurement
Multi-step chain.
PATTERNS
Production details.
Namespace isolation
Per org tenant.
Learn more →Shared visibility
Lifecycle across boundaries.
Cross-org audit
audit.record(org="vendor", action="approved", intent_id=...)
Cross-org setup
Create namespaces per organization; map identities to assignees on each wait. Use multi-tenancy for credential and data isolation. Define SLAs with timeout and escalation per leg.
Legal review export format with both parties before production — compliance teams sign off on wording.
Common questions
- External users need AXME accounts?
- Delivery modes can surface tasks in partner portals or email — integration pattern depends on deployment.
- Data residency?
- Enterprise deployments configure region and retention per tenant requirements.
- Audit for both sides?
- Intent audit can export views scoped per namespace for each organization's records.
Related reading
Deeper dives from the AXME blog.
A Two-Step Approval Chain Shouldn't Need a Workflow Engine
Manager approves, then finance approves. Simple enough to describe. 300 lines of code to build. Unless your platform handles approval chains natively.
Read post →How to Add Human Approval to AI Agent Workflows Without Building It Yourself
Adding a human approval step to an AI agent workflow means building a notification service, reminder scheduler, escalation chain, and webhook handler. Or you can use 4 lines of code.
Read post →
Related capabilities
Related links
Ship your first durable agent — in under 10 minutes.
Free tier. No credit card. Self-host or hosted — your choice.