Native Document Signing — Without DocuSign
Multi-party e-signature built into Salesforce. Drawn signatures via HTML5 canvas, SHA-256 hash chain audit trail, auto-generated Certificate of Completion, and token-gated portal signing. Zero external dependencies.
Why we built this natively
DocuSign charges per envelope. Adobe Sign charges per transaction. Both require external authentication, API callbacks, and a separate vendor relationship your compliance team needs to review.
But e-signature is not magic. At its core, it is three things: a record that someone consented, a tamper-evident chain of evidence, and a rendered image of their mark. Those are data model decisions, not billion-dollar SaaS products.
We built document signing as a first-class feature of Delivery Hub because the data model was already there. ActivityLog__c already tracks who-did-what-when. The portal already handles token-gated access. The document engine already generates PDFs. All we needed was a hash chain and a canvas.
Built in 5 Phases + Hardening
From data model to drawn signatures to ESIGN compliance. Each phase shipped incrementally and is fully tested.
Data Model
ShippedDocumentAction__c (master-detail child of DeliveryDocument__c) and DocumentTemplateSlot__mdt establish the schema. Each signer gets a slot with a unique 64-char hex token.
Text-Stamp Signing
ShippedAdmin-side signing: typed name rendered as a text stamp on the document. Fast, simple, works for internal approvals where drawn signatures aren't required.
Portal Signing
ShippedTenant or client signs via a token-gated URL on the public portal. No Salesforce login, no account creation. Open the link, review the document, sign.
SHA-256 Hash Chain + Certificate
ShippedEvery signature action is hashed and chained to the previous hash, creating a tamper-evident audit trail. Auto-generated Certificate of Completion with every signer's IP, timestamp, and consent record. ESIGN/UETA compliant.
Canvas Drawn Signatures
ShippedFull HTML5 canvas signature pad supporting mouse, touch, and Apple Pencil. Smooth Bezier curve rendering. The signer draws their actual signature, not just a typed name.
Hardening
ShippedFOR UPDATE race condition fix (prevents double-signing), canvas signature REST persistence, IP address capture on every signing event, token rotation to null on completion.
What You Get
Everything you need for production document signing. No add-ons, no external services, no per-envelope pricing.
Multi-party signing
Any number of signers, in any order. Each signer gets their own token-gated slot. Supports both sequential and parallel signing patterns.
Drawn signatures
HTML5 canvas with mouse, touch, and Apple Pencil support. Bezier curve smoothing for natural-looking signatures. Not just text stamps.
Hash chain audit trail
SHA-256 hash of every signing action, chained to the previous hash. Rides the existing ActivityLog__c infrastructure. Tamper-evident by construction.
Certificate of Completion
Auto-generated PDF with every signer's name, IP address, timestamp, consent record, and document hash. The proof that the document was signed.
Token-based security
Each signer slot gets a unique 64-character hex token. The token grants access to exactly one document. On completion, the token rotates to null — the link dies.
4 template slots included
Client_Agreement (Consultant + Client) and Contractor_Agreement (Company + Contractor) ship out of the box. Add your own via DocumentTemplateSlot__mdt.
ESIGN & UETA Compliance
The federal ESIGN Act and the Uniform Electronic Transactions Act (UETA) require four things for an electronic signature to be legally binding:
- Intent to sign — the signer takes an affirmative action (drawing their signature on the canvas or clicking “Sign”)
- Consent to do business electronically — recorded as a boolean consent flag before the signing action
- Association of signature with the record — the DocumentAction__c record links the signer, the document, and the signature image via master-detail
- Record retention — the SHA-256 hash chain and Certificate of Completion are stored permanently in Salesforce with the document
The auto-generated Certificate of Completion bundles all four elements into a single PDF: signer name, IP address, timestamp, consent record, document hash, and the full hash chain. This is the artifact you hand to a lawyer or auditor.
No per-envelope fee. Ever.
$0
Ships in the free package
DocuSign Business starts at $25/user/month with per-envelope overages. Delivery Hub's native document signing ships in the free package. Send unlimited documents, collect unlimited signatures, generate unlimited certificates. The only cost is your existing Salesforce license.
DocuSign vs Delivery Hub
Sign Documents Inside Salesforce
Install Delivery Hub. Generate a document from a template. Send the signing link. Drawn signature, hash chain, and Certificate of Completion — all native, all free.