A document envelope is one record that carries everything a document workflow produces. It holds the files you send, the controls on the link, the read sessions of every viewer, the signers and their order, and the audit trail of what happened when. When people say they sent an envelope, they mean they sent a document with its whole paper trail attached.
Why not just send the file?
A file proves nothing on its own. Email tells you a message was delivered. It does not tell you the attachment was opened, read past page one, or signed by the person you addressed. The envelope keeps the evidence and the document together. That way, sent is not the last thing you know.
What does an envelope contain?
Documents: one or more files, kept in order, with page edits like reorder or delete applied before sending.
Link controls: password, expiry, allowed emails and domains, download and print rules, and revoke.
Read evidence: viewer sessions with time per page, return visits, device, and region.
Signers: each with a role (signer, approver, witness, CC), a routing order, and an optional identity check before signing.
Audit events: created, sent, opened, page viewed, consented, identity verified, signed, completed, and more. Each one carries a timestamp.
How does routing work inside an envelope?
Signers can be routed one at a time, all at once, or in a mix of both. When identity verification is on, each signer confirms a one-time code sent to their email before signing. Every verification lands in the same audit trail as the reads.
What happens when an envelope completes?
Completion seals the record. The envelope issues a certificate of completion with cryptographic hashes of the signed PDF and its audit log. Anyone can check the result on a public verification page, with no account needed. The read history from before signing stays attached. That is the point.
