The three apps
The three Docusign apps for Salesforce.
| App | What it does | Legal’s role |
|---|---|---|
| eSignature for Salesforce | Send and sign from Salesforce records, with status and signed documents written back. | Signature authority and sending policies. |
| Docusign Gen for Salesforce | Generates agreements natively in Sales Cloud and Revenue Cloud (CPQ, Billing), merging customer, product and pricing data into Word or PDF. | Owns the templates and approved language. |
| Docusign CLM for Salesforce | Runs the contract lifecycle from the opportunity: generate, negotiate, approve and store. | Owns clauses, playbooks and approval rules. |
All three are installed and administered through the Docusign Apps Launcher, which connects accounts, maps Salesforce objects and manages users. Per Docusign’s Salesforce integration page, October 2026.
Out of the box or custom
What works out of the box, what takes process design, and what takes custom work.
Most disappointment with the integration comes from expectations nobody set. We agree these before anyone builds.
| Scenario | What to expect | What we recommend |
|---|---|---|
| Start a contract from the opportunity | Supported out of the box: record data populates the template. | Decide which Salesforce fields legal trusts in a contract, and lock the rest. |
| Status and the signed copy back in Salesforce | Supported out of the box. | File the executed copy in the governed repository as well. |
| Salesforce data changes mid-draft | Possible, but a restart discards work once negotiation has started. | See the next section. |
| Negotiated terms back into Salesforce fields | Usually needs field mapping, sometimes custom work. | Map only the fields sales and finance actually report on. |
| Custom objects, multiple entities, or approvals across Salesforce and CLM | Usually needs custom configuration or development. | Scope it up front, so the value is not left on the table. |
Mid-draft changes
When Salesforce data changes mid-draft.
At a Fortune 1000 financial services firm, the business wanted every contract to restart mid-draft whenever the Salesforce data behind it changed. Whether that is a good idea depends on where the contract is.
| Stage | Recommendation |
|---|---|
| Before negotiation starts | Regenerating the draft from the updated record is reasonable, and keeps the data and the contract in sync. |
| After the counterparty has redlined | A restart throws away negotiated language. Update the affected terms in place, or route the change to legal. |
| Always | Define which field changes trigger a regeneration, which update the draft, and which only notify the contract owner. |
Where integrations break
Where Docusign Salesforce integrations break.
The six problems raised most often in Docusign’s community, and their usual causes.
| Symptom | Usual cause |
|---|---|
| Users get errors opening records | The package was not installed for all users, or users were not added in Apps Launcher user management. |
| Users must re-authorize, or see consent errors | Salesforce connected-app policy changes revoke existing tokens. |
| Envelopes complete but nothing writes back | The system user needs re-authorizing, often after a plan or account change. |
| Object mapping never finishes | Custom object mapping can stall; it usually needs a support case. |
| Automations stop firing | Legacy-package actions built for Process Builder do not fire in Flows, and old and new packages share field names. |
| CLM does not appear in the Apps Launcher | The CLM account must be connected from Apps Launcher setup before upgrading. |
From Docusign community answers as of October 2026 (Apps Launcher, object mapping, Flows). Confirm fixes with Docusign support.
Case study
Rescuing a stalled CLM rollout at a Fortune 1000 financial services firm.
A global financial services firm had spent over a year on its CLM implementation without a successful go-live. Sales intake ran on a Salesforce-based solution, with a third-party CLM and Docusign, and several technology teams, consultants and vendors were involved. Our professionals were brought in to support the COO and drive the program to launch.
01
Diagnose and stabilize
An independent assessment of the in-flight build; Salesforce, sales, deal desk, legal and finance aligned on one target model; the plan reset with clear owners and acceptance criteria.
02
Rebuild on best practices
Repository design guided, 30 core templates evaluated, workflows defined and hardened with the Salesforce team, and contract initiation streamlined.
03
Test, train and go live
UAT plans and scripts for every persona, iterative test cycles with defects triaged to resolution, and a detailed go-live plan.
Result: the stalled rollout was stabilized, with an accountable plan to roll out contract lifecycle management for 30+ contract types.
Read the case study →How to scope it
How to scope a Docusign Salesforce integration.
01
Inventory
Docusign accounts, installed packages, objects, templates and automations in use today.
02
Decide the system of record
Which system owns the template, where the executed copy is filed, and which fields flow back.
03
Map objects and fields
Agree the mapping with sales operations and legal before anything is built.
04
Build and test in a sandbox
Run real deals through it before go-live.
05
Govern
Permissions, sending policies and a named owner for changes.
How we help
How we help.
01
Set expectations
What the standard Salesforce integration will and will not do, agreed before anyone builds.
02
Process design
How contracts start from Salesforce, how changes mid-draft are handled, and who owns each step.
03
Custom work
The configuration or development that gets the full value: field write-back, custom objects, approval logic.
04
Fix or rescue
Broken setups and stalled rollouts, stabilized and taken to go-live.
Who you work with
The practitioners behind the integration.
Gary Wheeler
CLM & AI Lead
Has built CLM programs and created legal ops teams for multiple Fortune 500 companies, including Home Depot and Cox. Delivery experience across Docusign CLM and Onit CLM.
Danish Butt
Managing Director
20+ years, including Huron Consulting and Morae Global. Leads legal technology and contracting programs for corporate law departments, from selection through adoption.
Frequently asked questions
How does Docusign integrate with Salesforce?
Through three apps: eSignature for Salesforce to send and sign from Salesforce records, Docusign Gen for Salesforce to generate agreements from Salesforce data, and Docusign CLM for Salesforce to run the contract lifecycle from the opportunity. All three are installed and administered through the Docusign Apps Launcher, which connects accounts, maps objects and manages users.
What is Docusign Gen for Salesforce?
Docusign Gen for Salesforce generates agreements natively inside Sales Cloud and Revenue Cloud, including CPQ and Billing, by merging customer, product and pricing data from Salesforce into Word or PDF documents. Legal should own the templates and the approved language in them.
What is the Docusign Apps Launcher?
The Docusign Apps Launcher is the managed package used to install and administer Docusign's Salesforce apps. Admins use it to connect Docusign accounts, map Salesforce objects and manage which users can send. Many integration problems trace back to how it was installed or how users were added.
Do we need Docusign eSignature or Docusign CLM in Salesforce?
eSignature for Salesforce is enough to send and sign from Salesforce records. Add Docusign Gen when agreements should be generated from Salesforce data. Choose Docusign CLM when legal negotiates, approves and manages contracts at volume and needs clauses, playbooks and a repository behind the opportunity.
Why did Docusign stop writing back to Salesforce?
The usual causes are a system user that needs re-authorizing after a plan or account change, Salesforce connected-app policy changes that revoked tokens, users missing from Apps Launcher user management, or automations built on the legacy package that do not fire in Flows. Confirm the fix with Docusign support.
What can the Docusign Salesforce integration not do out of the box?
Starting a contract from the opportunity and writing status and the signed copy back are supported out of the box. Writing negotiated terms back into Salesforce fields usually needs field mapping and sometimes custom work, and custom objects, multiple entities or approval logic spanning Salesforce and the CLM usually need custom configuration or development. Agree these expectations before the build starts.
Should a contract restart when Salesforce data changes mid-draft?
Only before negotiation starts. Regenerating the draft from the updated record keeps data and contract in sync at that stage. Once the counterparty has redlined, a restart throws away negotiated language, so update the affected terms in place or route the change to legal. Define which field changes trigger a regeneration, which update the draft, and which only notify the contract owner.
Connecting Docusign and Salesforce? Talk to a practitioner first.
Book a Discovery CallDocusign pages
Part of our Docusign consulting practice.
Also relevant: Case study: Fortune 1000 financial services