Docusign Salesforce Integration: Setup, Templates and Pitfalls (2026 Guide)

What a Docusign Salesforce integration should do

The goal is simple: a contract leaves Salesforce, gets signed, and the result lands back on the same record without anyone copying data. A working Salesforce Docusign integration does five jobs:

• Send from the record. A button on the opportunity, quote, account or custom object opens a prepared envelope.
• Fill the document. Customer name, address, amount and terms come from Salesforce fields, not from a rep’s typing.
• Pick the right signers. Recipients come from the record: the opportunity’s contact, the account owner, a legal approver.
• Track status. Sales and finance see sent, delivered, completed or declined without leaving Salesforce.
• Write back. The signed PDF is saved to the record, and fields such as Stage update when the envelope is completed.

If you only need the first and last jobs for a handful of deals a month, the standard package with one template is enough. Volume, approvals and generated documents are what make the project bigger.

Which Docusign app for Salesforce you need

As of October 2026, Docusign ships its Salesforce apps in one managed package, Docusign Apps Launcher for Salesforce. According to Docusign’s installation guide, it includes eSignature for Salesforce, CLM for Salesforce and Gen for Salesforce, and installing any one of them installs the complete package.

Docusign’s admin guide also lists CLM Essentials and the eSignature Apex Toolkit as parts of it. What you can use depends on what your Docusign account is licensed for.

One timing note: Docusign’s support center says Apps Launcher version 8.6.1 or higher is needed for Salesforce’s new connected app security requirements. Docusign set October 8, 2026 as the enforcement date for Apps Launcher and pushed upgrades to production orgs between September 5 and October 5, 2026.

On older versions, new users cannot authorize the app. Check your installed version under Installed Packages before you start.

Legacy eSignature for Salesforce vs. Apps Launcher

Some older orgs still have the first Docusign package installed, now called legacy Docusign eSignature for Salesforce. According to Docusign, it was de-listed from the marketplace in 2020, and its end-of-service date was October 16, 2026. Docusign’s migration article says the legacy app and its CPQ version cease to function and are no longer supported after that date.

If it is still in your org, move now. Docusign offers a migration tool for users, templates and records. After migrating, you remove the legacy permission sets, components and buttons before uninstalling.

Docusign also offers Docusign for Agentforce for sending agreements from pre-approved templates inside Agentforce. Its own page notes that some features are subject to future availability, so treat it as an add-on to the setup below, not a replacement.

What it costs on the Docusign side

Docusign’s eSignature pricing page lists, as of October 2026, Standard at $30 and Business Pro at $45 per user per month (on an annual commitment), each with 100 envelopes per user per year. In the plan comparison on the same page, “Integrations to Salesforce, Microsoft Dynamics, and Netsuite” and “Docusign Gen for Salesforce” are marked “Does not include” for the Personal, Standard and Business Pro plans, and the Enhanced plans show “Contact sales”. Ask Docusign sales which Enhanced plan covers your use, including Gen or CLM, before you build anything.

Your options compared

Docusign’s package is the default answer to “docusign integration with salesforce”, but not the only one. Here are four routes, from the package itself to your own build:

A few facts on the alternatives, from each vendor’s documentation as of October 2026:

• Adobe says Acrobat Sign for Salesforce supports Professional, Enterprise, Unlimited, Developer and Performance editions.
• Dropbox Sign’s integration needs a Dropbox Sign Enterprise plan with Salesforce enabled.
• PandaDoc sells its Salesforce integration as a paid add-on for Business and Enterprise annual plans.

If you already standardized on one of them for other reasons, compare its Salesforce package before switching e-signature vendors.

Which option fits you?

Where your contracts are drafted and who reviews them decide most of this. Five questions on that, plus orgs and vendors, point you to eSignature alone, Gen, CLM or a custom build.

How the data flows

Salesforce stays the system of record for the deal and the customer. Docusign is the system of record for the envelope: who signed what and when. The package moves data both ways at fixed points.

Template and field mapping: what goes where

In Apps Launcher, the mapping lives in the envelope template. You pick a Salesforce object as the data source, and everything else hangs off it. Start with this set:

Docusign’s guide sets a few limits worth knowing before you design templates:

• Merge fields can reach fields up to four levels of relationship from the source object, through lookups and child objects. Related list fields are out of reach; they need Docusign’s document custom fields instead.
• Field updates allow up to five per envelope event type, and two updates for the same event cannot target the same field.
• Reminders and expiration go up to 999 days.
• On Salesforce mobile, Docusign’s guide describes sending with Quick Send and Send Now templates.

Two rules save most of the pain. Make Salesforce the only place where deal data is edited, and allow writeback only on fields a signer is genuinely meant to correct, like a billing address or PO number. Never let a signer write back the amount without a review step.

How to set it up, step by step

The sequence below follows Docusign’s eSignature for Salesforce admin guide, with the template design and the integration users settled before anything is installed. Docusign renames menus from time to time, so take the exact clicks from its current guide.

1. Write down the flowWhich object you send from, which documents, who signs in what order and what must be written back. Add what happens in Salesforce when the envelope is completed or declined. This becomes your template design.
2. Prepare a sandbox and a Docusign demo accountCreate a Docusign developer (demo) account for testing. Docusign’s guide connects sandboxes to demo accounts; production Salesforce connects to a production Docusign account.
3. Create the integration usersOn the Salesforce side, use a generic user on a Standard User license with System Administrator access. A cloned standard profile with the permissions Docusign lists (API Enabled, Manage Users, Customize Application and others) also works. Set “Multi-Factor Authentication for API Logins” to off for that profile. On the Docusign side, a generic administrator nobody logs in with day to day. Docusign notes that the Salesforce Integration User license can’t be used, because those users can’t be added to the Docusign Administrator permission set.
4. Install Apps LauncherFrom AgentExchange, sign in with production admin credentials even for a sandbox install, choose sandbox or production, and install for all users. Make sure the version is 8.6.1 or later.
5. Connect the accountsOpen Docusign Apps Launcher, go through Docusign Setup and authorize with the Salesforce and Docusign integration users. For a demo account, choose “Log in to Demo Account” under advanced options. One Docusign account connects to one Salesforce org.
6. Add usersGive each sender a Docusign user from the Docusign user management page (eSignature User or Administrator). Existing Docusign users can instead self-activate through the Docusign Login permission set. Don’t add people to the other Docusign permission sets by hand. Names and emails must match in both systems.
7. Add components to layoutsPut the Envelope Status component (and Docusign Files if you use it) on the opportunity or quote page so users see progress.
8. Build the first envelope templateIn the Envelope Templates tab: name and data source, documents, recipients, merge fields, field placement, then options (sending experience, reminders, expiration, document writeback and field updates). The last step adds a custom button to the layouts you choose.
9. Automate if neededFor sends without a click, add the Send with Docusign action to a record-triggered Flow (Apps Launcher 6.1 or later) with the template ID and the record ID.
10. Test real scenariosTry a normal deal, two signers in order and a signer who edits a writeback field. Add a declined envelope, a voided envelope, a contact with a Salesforce contact role and a send from console view. Check the status records, files and fields on the record after each.
11. Pilot, then go to productionRun one sales team for a week or two, then repeat the setup in production. Templates don’t move by themselves: rebuild or clone them, and note that a later sandbox refresh points the sandbox back at production’s Docusign connection.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

The Salesforce side of the integration user deserves its own design. Our guide to the Salesforce integration user covers licenses, profiles and permission sets for integrations in general.

Contract management software and Salesforce: Gen and CLM

eSignature only sends a document you already have. If reps still build quotes in Word, Docusign Gen for Salesforce fills a template with record data and line items. It puts a Generate button on the record, and the result goes to eSignature. Docusign’s documentation also says eSignature customers who buy Salesforce CPQ Plus receive a Docusign Gen license, subject to prerequisites such as a paid multi-user Docusign account.

When legal reviews contracts, the need is contract lifecycle management. Docusign CLM for Salesforce adds a repository, approval and review workflows and document generation, all launched from Salesforce.

Any contract management software Salesforce integration raises the same questions: which system holds the final contract, which fields come back to the opportunity, and who owns the template library. Settle those before choosing between Gen, CLM or a third-party CLM.

If finished contracts must also be filed in a document library, see our Salesforce SharePoint integration guide.

When a custom Docusign integration makes sense

The package covers sending from Salesforce records. A custom build on the Docusign eSignature REST API and Docusign Connect starts to pay off when:

• Signing starts outside Salesforce: a customer portal, an onboarding app or a checkout, with results stored in Salesforce.
• You need several Salesforce orgs on one Docusign setup, which the package doesn’t support.
• Completed envelopes must trigger other systems too: billing, provisioning, an ERP or a document archive.
• Writeback needs rules the template options can’t express, such as approval before a signer’s change lands.

A typical build has three parts:

• Sender. A service creates envelopes from templates through the REST API.
• Listener. A webhook listener receives Connect events. Docusign describes Connect as a webhook service that posts to a public HTTPS listener and retries failed deliveries with back-off for up to 15 days. Docusign prefers it over polling, which it limits to once every 15 minutes per envelope.
• Writer. It updates Salesforce through its APIs idempotently, so a retried event never creates a second file or flips a stage twice.

Inside Salesforce, the Apex Toolkit is a lighter option for sends that stay in the org. Our Salesforce API integration guide covers the Salesforce side.

The ranges are taken from our API integration cost guide, which also explains what makes a build land at the cheap or the expensive end. For connecting Salesforce to other systems in general, see the Salesforce integration guide.

Go-live checklist

Run through these before the first customer receives an envelope. Most items map to a pitfall described above, so an unchecked box is a known risk, not a formality.

FAQ

Where Gilzor fits

A Docusign rollout touches sales, legal and the Salesforce admin, and the package only works once all three agree on the contract flow. As a software development company with a team in Poland and Cyprus, Gilzor builds and maintains Salesforce integrations; for Docusign, that starts with mapping the flow together with sales and legal.

Then we set up or clean up the Docusign package and its templates, or build a custom integration on the Docusign and Salesforce APIs, and stay on to support it after launch. The Salesforce integration services page shows how such projects are scoped.