Knowledge Base › PDF Signing › Multi-Signature Workflows

Multi-Signature Workflows

Apr 5, 2026 · 506 views

Many documents need more than one signature — Prepared by / Reviewed by / Approved by, or a personal signature plus an organisation seal. OneSigner supports all of these patterns while keeping every signature cryptographically valid.

How PDF Multi-Signing Works

Each signature is applied as an incremental update to the PDF: new data is appended, nothing already signed is rewritten. That is why signature #1 remains valid after signature #2 is added — Adobe Acrobat shows every signature with its own certificate, timestamp and validity status.

Pattern 1: Multiple Signatures in One Profile (Automated)

  1. In the signing profile, add multiple signature configurations.
  2. Give each its own certificate and anchor text, e.g.:
    • Signature 1 — Certificate A, find text "Prepared by"
    • Signature 2 — Certificate B, find text "Approved by"
  3. Enable the profile. Every file that passes through is signed with all configured signatures, in order.

Requirements: all USB tokens plugged in at the same time, and a PIN stored for each certificate.

Pattern 2: Sequential Signers via eSign (Human Workflow)

When different people must sign in order, use the eSign portal instead: add multiple recipients to a signature request, and OneSigner emails each signer in turn — signer 2 only receives their link after signer 1 has finished. Each signer's fields are applied without disturbing earlier signatures, so every digital signature stays valid. See Sending a Document for Signature.

Pattern 3: Electronic Signature + Organisation Seal

In the eSign portal, signers without a USB token can sign electronically (draw/type); OneSigner then seals the document with your organisation's digital certificate, giving the file cryptographic integrity on top of the electronic signatures. See The Signer Experience.

Verification Notes

  • Open the signed PDF in Acrobat → Signature Panel: each signature lists its signer, time, and "document has not been modified" status.
  • A signature only covers the document revision that existed when it was made — later signatures appear as additional revisions. This is standard PDF behaviour and exactly what auditors expect.
  • If any earlier signature shows as broken after further processing, the file was modified by a non-incremental tool — always keep OneSigner (or another incremental-update signer) last in your pipeline.