Multi-Party Signing Workflows

Many agreements require signatures from multiple parties. sajn supports flexible signing workflows, from simple parallel signing to complex sequential approval chains.

Understanding Signing Orders

sajn offers three approaches for multi-party signing:

Type	Description	Use Case
Parallel	Everyone signs at the same time	NDAs, simple contracts
Sequential	One after another in order	Approval chains, escalations
Mixed	Some parallel, some sequential	Complex workflows

Parallel Signing

In parallel signing, all signers receive the document at the same time and can sign in any order.

Configuration

Set all signers to the same signingOrder:

curl -X POST https://app.sajn.se/api/v1/documents \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Non-Disclosure Agreement",
    "type": "SIGNABLE",
    "documentMeta": {
      "signingOrder": "PARALLEL"
    },
    "signers": [
      {
        "name": "Anna Andersson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 1,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      },
      {
        "name": "Erik Eriksson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 1,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      }
    ]
  }'

When to Use Parallel Signing

NDAs where both parties need to agree
Simple contracts with equal parties
Time-sensitive documents where speed matters
Multi-party agreements without dependency requirements

Parallel signing is faster because signers don’t wait for each other. Use it when there’s no requirement for a specific signing sequence.

Sequential Signing

In sequential signing, signers receive the document one at a time in a specified order. Each signer is emailed (or sent an SMS) only when it becomes their turn — a downstream signer gets no notification at send time. The next signer is contacted automatically after the previous step is complete.

Until a signer’s turn arrives they have not been contacted, and in the dashboard they show as “Väntar på tur” (Waiting for turn) rather than “Sent”. This is expected — it is not a delivery failure.

Configuration

Set incrementing signingOrder values:

curl -X POST https://app.sajn.se/api/v1/documents \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Employment Contract",
    "type": "SIGNABLE",
    "documentMeta": {
      "signingOrder": "SEQUENTIAL"
    },
    "signers": [
      {
        "name": "Anna Andersson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 1,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "DRAWING"
      },
      {
        "name": "Maria Johansson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 2,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      },
      {
        "name": "Erik Eriksson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 3,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      }
    ]
  }'

Signing Flow

Step 1: Anna receives the document and signs
Step 2: After Anna signs, Maria receives the document
Step 3: After Maria signs, Erik receives the document
Completed: All three have signed

When to Use Sequential Signing

Approval chains where manager approval is needed first
Hierarchical signatures (employee → manager → executive)
Counter-signatures where one party must sign first
Legal requirements for specific signing order

Mixed Workflows

For complex scenarios, combine parallel and sequential signing:

curl -X POST https://app.sajn.se/api/v1/documents \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Partnership Agreement",
    "type": "SIGNABLE",
    "documentMeta": {
      "signingOrder": "SEQUENTIAL"
    },
    "signers": [
      {
        "name": "Anna Andersson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 1,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      },
      {
        "name": "Erik Eriksson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 1,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      },
      {
        "name": "Maria Johansson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 2,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      },
      {
        "name": "Johan Svensson",
        "email": "[email protected]",
        "role": "SIGNER",
        "signingOrder": 2,
        "deliveryMethod": "EMAIL",
        "requiredSignature": "BANKID"
      }
    ]
  }'

Signing Flow

Step 1 (Parallel): Anna and Erik from Company A sign simultaneously
Step 2 (Parallel): After both sign, Maria and Johan from Company B sign simultaneously
Completed: All four have signed

Signers with the same signingOrder value sign in parallel. The next order group only receives the document when all previous signers have completed.

Tracking Progress

Document Status

Track overall document progress:

curl -X GET https://app.sajn.se/api/v1/documents/doc_123 \
  -H "Authorization: Bearer YOUR_API_KEY"

Response shows signing status:

{
  "document": {
    "id": "doc_123",
    "name": "Employment Contract",
    "status": "SENT",
    "signers": [
      {
        "signerId": "signer_1",
        "name": "Anna Andersson",
        "status": "SIGNED",
        "signedAt": "2024-01-15T10:30:00Z"
      },
      {
        "signerId": "signer_2",
        "name": "Maria Johansson",
        "status": "PENDING",
        "signedAt": null
      }
    ]
  }
}

Signer Statuses

Status	Description
`PENDING`	Waiting for earlier signers (sequential)
`NOTIFIED`	Document sent, awaiting signature
`OPENED`	Signer has viewed the document
`SIGNED`	Signer has completed signing
`REJECTED`	Signer has declined to sign

Webhook Notifications

Each individual signature fires DOCUMENT_PARTY_SIGNED, carrying the Document + Party payload — the whole document plus the party that just signed:

{
  "event": "DOCUMENT_PARTY_SIGNED",
  "payload": {
    "document": {
      "id": "clx1abc...",
      "title": "Partnership Agreement",
      "status": "PENDING",
      "parties": [...],
      "signers": [...]
    },
    "party": {
      "id": "clx3ghi...",
      "name": "Anna Andersson",
      "email": "[email protected]",
      "externalId": null,
      "signingStatus": "SIGNED"
    }
  },
  "createdAt": "2026-01-15T10:30:00.000Z",
  "webhookEndpoint": "https://your-server.com/webhook"
}

There is no remainingSigners count — derive it from payload.document.parties by counting the ones still NOT_SIGNED. Once every signing party is done, a separate DOCUMENT_SIGNED event fires with the plain Document payload.

Common Patterns

Manager Approval Before Employee

Employee signs first, then manager approves:

{
  "signers": [
    {
      "name": "Anna Andersson",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 1
    },
    {
      "name": "Erik Manager",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 2
    }
  ]
}

Multiple Counterparties

Your company signs first, then the client:

{
  "signers": [
    {
      "name": "Your CEO",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 1
    },
    {
      "name": "Client Representative",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 2
    }
  ]
}

Witness Signatures

Main parties sign, then witnesses attest:

{
  "signers": [
    {
      "name": "Party A",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 1
    },
    {
      "name": "Party B",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 1
    },
    {
      "name": "Witness 1",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 2
    },
    {
      "name": "Witness 2",
      "email": "[email protected]",
      "role": "SIGNER",
      "signingOrder": 2
    }
  ]
}

Board Resolution

All board members must sign:

{
  "documentMeta": {
    "signingOrder": "PARALLEL"
  },
  "signers": [
    { "name": "Board Member 1", "signingOrder": 1 },
    { "name": "Board Member 2", "signingOrder": 1 },
    { "name": "Board Member 3", "signingOrder": 1 },
    { "name": "Board Member 4", "signingOrder": 1 },
    { "name": "Board Member 5", "signingOrder": 1 }
  ]
}

Best Practices

Consider signer availability

For sequential signing, consider whether signers will be available. A single unavailable signer blocks the entire chain.

Use parallel when possible

Parallel signing is faster and reduces bottlenecks. Only use sequential when there’s a business requirement.

Set appropriate expiration

For multi-party documents, allow extra time for all parties to sign. Consider longer expiration periods.

Configure reminders

Enable automatic reminders to keep the signing process moving, especially for sequential workflows.

Handle rejections gracefully

If any signer rejects, the document is rejected. Have a process for handling rejections and restarting if needed.

Track with webhooks

Use webhooks to monitor signing progress and take action when documents are signed, rejected, or stalled.

Next Steps

Reminders & Expiration

Configure reminders and document expiration

Webhooks

Track signing progress in real-time

Creating Documents

Learn document creation basics

Signers Concept

Understand signer types and roles

​Multi-Party Signing Workflows

​Understanding Signing Orders

​Parallel Signing

​Configuration

​When to Use Parallel Signing

​Sequential Signing

​Configuration

​Signing Flow

​When to Use Sequential Signing

​Mixed Workflows

​Signing Flow

​Tracking Progress

​Document Status

​Signer Statuses

​Webhook Notifications

​Common Patterns

​Manager Approval Before Employee

​Multiple Counterparties

​Witness Signatures

​Board Resolution

​Best Practices

​Next Steps

Reminders & Expiration

Webhooks

Creating Documents

Signers Concept

Multi-Party Signing Workflows

Understanding Signing Orders

Parallel Signing

Configuration

When to Use Parallel Signing

Sequential Signing

Configuration

Signing Flow

When to Use Sequential Signing

Mixed Workflows

Signing Flow

Tracking Progress

Document Status

Signer Statuses

Webhook Notifications

Common Patterns

Manager Approval Before Employee

Multiple Counterparties

Witness Signatures

Board Resolution

Best Practices

Next Steps