Set Up Native E-Signature in Salesforce with Dochly
What is native e-signature in Dochly?
Dochly's native e-signature is a 100% Salesforce-native signing experience — no DocuSign, Adobe Sign, or other third-party platform required. Documents are sent directly from Salesforce, signers sign through a secure browser link, and completed documents are stored back on the Salesforce record automatically.
Native e-signature (this guide)
- No external platform or additional subscription
- Sending, tracking, and storage all within Salesforce
- Signed documents automatically stored as Salesforce Files
- Signature fields placed in Dochly template editor
- Audit trail stored natively on the Salesforce record
DocuSign / Adobe Sign integration
- Requires separate subscription to external platform
- Documents leave Salesforce for signing
- Completed documents sync back via integration
- Configuration managed in the external platform
- Subject to external platform availability
Before you set up
Confirm these prerequisites before configuring e-signature settings:
E-signature is part of the Dochly package — it's available once Dochly is installed and the connection status is green. See Install Dochly from AppExchange if not yet done.
E-signature settings are only accessible to users with the Dochly Admin permission set. Confirm it's assigned to your user in Setup → Users → Permission Set Assignments.
E-signature request emails are sent through Salesforce. Go to Setup → Email → Deliverability and confirm it is set to All Email — not "System Email Only". Without this, signature request emails won't reach signers.
E-signature only works with PDF output documents. You need at least one Active Dochly template set to PDF output before you can test the full signing workflow after setup.
Step-by-step: setting up e-signature
Enable e-signature in Dochly Settings
Open the Dochly app → Settings → E-Signature. Toggle Enable E-Signature to on. Once enabled, the Send for Signature button becomes available on generated documents, and e-signature options appear in the template editor.
If the E-Signature section doesn't appear in Settings, your Dochly plan may not include the e-signature feature. Check your plan details or contact Dochly support.
Configure signer authentication
Authentication controls how signers verify their identity before signing. Choose the level appropriate for your use case:
Settings → E-Signature → Authentication
RequiredSigner clicks the link in the email — no additional identity verification. Fastest signing experience for low-risk documents.
Recommended for: proposals, quotes, order confirmationsSigner receives a one-time passcode to their email before accessing the document. Medium security — confirms the signer has access to the inbox.
Recommended for: contracts, NDAs, standard agreementsSigner receives a one-time passcode via SMS. Requires the signer's mobile number. Higher security than email OTP.
Recommended for: financial documents, legal agreements, high-value contractsSet consent language
The consent statement is shown to signers before they can sign — it confirms they agree to sign electronically. This is required for ESIGN/UETA compliance in the United States and equivalent legislation in other jurisdictions.
Go to Settings → E-Signature → Consent Language. Options:
- Use Dochly default: Dochly-provided consent language reviewed against ESIGN/UETA requirements. Suitable for most use cases.
- Custom consent text: Enter your own legally approved language. Have this reviewed by your legal team before enabling.
Do not disable consent language or use a very short statement. The consent screen is a legal requirement in most jurisdictions — it demonstrates the signer knowingly agreed to sign electronically and understood what they were signing.
Configure post-signature document storage
Set what happens after all parties have completed signing:
Settings → E-Signature → Storage
RequiredAutomatically saves the fully signed PDF to the originating Salesforce record's Files list when all parties have signed.
Recommended: Always enable — critical for audit trailSends a copy of the signed document to all parties after completion. The sender, signer, and any CC recipients all receive the final signed PDF.
Recommended: Enable for customer-facing documentsOptionally update a field on the originating record when signing completes — e.g. Stage to "Contract Signed" or a checkbox to TRUE.
Recommended: Configure per your sales process stagesSet signing expiry and automatic reminders
Configure how long a signature request stays open and whether automatic reminder emails are sent to unsigned signers.
How long the signing link remains active. After expiry, the link stops working and a new request must be sent. Recommended: 14 days for most contracts, 7 days for time-sensitive documents. See the dedicated guide: Set up reminders and expiry.
Send automated reminder emails to signers who haven't signed yet. Recommended: first reminder at day 3, final reminder at day 7 before expiry. Reduces the need for manual follow-up on outstanding signatures.
Configure email branding
Customise the signature request email that signers receive — from name, from address, subject line, and email body. This is the first touchpoint signers have with the signing experience.
- From name: Your company name or team name — e.g. "Acme Corp Contracts"
- From email: A monitored company inbox — replies from signers go here
- Subject line: Clear and action-oriented — e.g. "Your agreement is ready to sign"
- Email body: Brief, professional message with a clear call-to-action button
Keep the email short and focused on the single action — click to sign. Long emails with multiple links reduce signing rates.
Verify the setup with a test signing
Before using e-signature with real customers, run a complete test:
- Generate a document from a test Opportunity record
- Click Send for Signature and enter your own email address as the signer
- Check your inbox for the signature request email
- Click the signing link and complete the signature
- Return to the Salesforce record and confirm the signed document appears in the Files list
If the test email doesn't arrive, check Salesforce Setup → Email → Deliverability (must be "All Email") and verify the from-email address in e-signature settings is a valid, monitored inbox. See e-signature troubleshooting for more.
Legal compliance overview
Dochly's native e-signature is designed to comply with the major e-signature legislation frameworks. Understanding the key requirements helps ensure your workflows meet the necessary standards.
Electronic signatures are legally binding in the US under the Electronic Signatures in Global and National Commerce Act (ESIGN) and the Uniform Electronic Transactions Act (UETA). Key requirements: signer consent to sign electronically (handled by Dochly's consent screen), intent to sign, and a complete audit trail. Dochly meets all three requirements when properly configured.
In the European Union, the eIDAS regulation governs e-signatures. Dochly provides Simple Electronic Signatures (SES) — legally valid for most commercial agreements. Advanced Electronic Signatures (AES) or Qualified Electronic Signatures (QES) may be required for specific regulated documents — consult your legal team for compliance-sensitive workflows.
For each signed document, Dochly records: signer email address, IP address, timestamp of signature, authentication method used, consent confirmation, and document hash. This audit trail is stored on the Salesforce record alongside the signed document.
Dochly's native e-signature is not suitable for documents that legally require wet (handwritten) signatures, notarization, specific government-issued ID verification, or Qualified Electronic Signatures under eIDAS. Consult your legal team for jurisdiction-specific requirements.
Frequently asked questions
Native e-signature is now configured in your Dochly org. Next step: Set up signature fields in a document template — add signature, initials, date, and text fields to your templates before sending your first request.
Rated 5 stars · Native Salesforce app · Free to install