Multi-Signer Routing

Aoexl supports both parallel and sequential signer routing.

Routing Modes

Parallel

All recipients can be invited immediately.

Sequential

Only the first signer is active at the start. Later signers wait until earlier signers complete.

Current Product Behavior

• request metadata stores routing mode and signing order
• sequential requests are created with waiting-turn status for later signers
• completion activates the next signer in the sequence
• local fallback sessions also support sequential advancement

Sequential Request Example

{
  "action": "bulk_create",
  "documentId": "doc_123",
  "documentName": "Merchant.pdf",
  "sourceDocumentPath": "user_123/doc_123.pdf",
  "routingMode": "sequential",
  "recipients": [
    {
      "signerName": "Jane Merchant",
      "signerEmail": "jane@example.com",
      "signingOrder": 1
    },
    {
      "signerName": "Alex Approver",
      "signerEmail": "alex@example.com",
      "signingOrder": 2
    }
  ]
}

In sequential mode, the first signer receives an active link immediately. Later signers remain queued until the previous signer completes.

Data Model Concepts

• request_group_id
• routing_mode
• signing_order
• is_active
• activated_at

Operational Notes

• the developer hub request history now shows grouped signer chains, per-signer status, and completion artifacts
• support teams should still verify whether next-signer activation happened via edge completion or local fallback when debugging unusual sequences