Skip to content
Browse help

How to

Send multi-document signing packets, handle delegation, and import executed contracts

Multiple agreements travel in one packet link, signers can delegate cleanly within their company domain, externally signed PDFs are recorded alongside your contracts, and anyone can verify a certificate.

  1. 1

    Create a packet at /packets/new and add signature documents plus read-only reference disclosures inside /packets so each recipient gets one consolidated link instead of separate emails per file.

    Documents · /packets/new; /packets

  2. 2

    When preparing a document for signature, choose ordered signing (signers unlock in sequence) or unordered signing. If a recipient is the wrong person, they can use self-service delegation to forward the link once to another person on the same email domain (cross-domain changes require the sender to resend).

    Documents · signing setup

    A request that was already forwarded by delegation cannot be delegated a second time; ask the sender to update the recipient instead.

  3. 3

    For contracts signed outside your workspace, open /agreements/documents/import, upload the executed PDF, optionally link it to a client, project, rental, or trial, and record the external signing provider and execution date.

    Work · /agreements/documents/import

  4. 4

    To confirm any completed Documents agreement has not been tampered with, open /agreements/verify with its signed PDF and attestation packet (or the completion email's verification token) to verify both the Ed25519 signature and the OpenTimestamps Bitcoin block anchor.

    Documents · /agreements/verify

Worth knowing

  • Executed external PDFs preserve a custody upload fingerprint and attestation, whereas documents signed in Documents carry an Ed25519 signature certificate and OpenTimestamps proof.