Dropbox Sign Salesforce integration: requirements, templates, text tags and limits
A plain-English guide to Dropbox Sign for Salesforce (formerly HelloSign): which plan you need, how the connected-user model works, why templates have to be created in Salesforce, how text tags behave, and the limits your admin and reps will hit. Then a look at what changes when proposals and signatures run natively inside Salesforce.
One adds a signing button and a request object to your records. The other builds, sends and tracks the whole proposal inside them.
Does Dropbox Sign integrate with Salesforce?
Yes. Dropbox Sign for Salesforce is a managed package on the AppExchange that adds a Use Dropbox Sign button and a Signature Requests related list to Accounts, Contacts, Leads and Opportunities, with other objects available after configuration. Reps send a template or a one-time document from the record, Salesforce fields merge into the document, and the signed copy comes back to the request record. The integration needs a Dropbox Sign Standard or Premium team with Salesforce enabled, runs through a single connected admin user, and every template must be built and maintained inside Salesforce rather than in the Dropbox Sign app.
What Dropbox Sign for Salesforce actually does.
A button and a related list
The package adds a Use Dropbox Sign button to supported records and a Dropbox Sign Signature Requests related list. Reps pick a template or upload a one-time document, choose signers, add a message and send. Request status and the completed document appear on the related list.
Merge and writeback fields
When a template is created in Salesforce, step four lets you pick merge fields from the source object so Salesforce data fills the document. Writeback fields let a signer edit a value during signing and have the response written back to the Salesforce field.
Text tags in generated documents
If another tool builds the PDF (a CPQ, a document generator), text tags such as [sig|req|signer1] placed in the source file are detected automatically and turned into signature, initial, date, text and checkbox fields when the document is sent from Salesforce.
How to set up Dropbox Sign for Salesforce, step by step.
Check the plan
Dropbox’s help centre says a paid customer needs a Dropbox Sign Standard or Premium team with the Salesforce add-on enabled (one article words it as an Enterprise plan with Salesforce enabled). A free Dropbox Sign account can install the package for a 30-day trial. Salesforce Professional, Enterprise, Unlimited and Developer editions work.
Pick the connected user carefully
The whole org runs through one connected user, who must hold the admin or developer role on the Dropbox Sign team, ideally the System Administrator profile in Salesforce, with the same email address in both systems. Every template and open request belongs to this connection.
Install from the AppExchange
Install Dropbox Sign for Salesforce for admins first, then assign the HelloSign_Admin and HelloSign_User permission sets. Sandbox first if you have one.
Connect and grant
Open the Dropbox Sign Settings tab, click Connect, sign in to Dropbox Sign and click Grant. Only the system administrator does this; other users send through the connection without their own Dropbox Sign accounts.
Configure any extra objects
Accounts, Contacts, Leads and Opportunities work out of the box. For anything else, add a lookup on the Signature Request object, build a Visualforce page with the HelloSign extension, create the button, add it and the related list to the layout, register the object in Supported Objects and clone the user permission set to include the page.
Build your templates in Salesforce
Eight steps per template: properties and source object, document upload, signer roles and order, merge and writeback fields, title and message, prepare, place fields in the editor, then publish. If the template relies on text tags, the file source must be File Attached to Record or the tags are not recognised.
Train reps on the two send paths
Template sends follow the fields you placed. One-time document sends let a rep upload any file, and text tags in it are detected on the fly. Both create a Signature Request record on the launching object.
Where Dropbox Sign for Salesforce stops.
None of these are hidden. They are in Dropbox’s own documentation, and they are the points where sales teams start looking for a Salesforce-native alternative.
Templates live in Salesforce only
“Templates must be created in Salesforce when using the Dropbox Sign for Salesforce integration.” Templates built in the Dropbox Sign app or through the API cannot be used from Salesforce and have to be recreated.
Integration FAQsEditing in the wrong place corrupts the template
Templates appear in the Dropbox Sign app but must not be edited there. Dropbox warns that edits made outside the Edit Template button in Salesforce “may corrupt the template and render it irretrievable.”
Template usage in SalesforceOne connected user for the whole org
Every template and request is owned by the admin who made the connection. Changing that user breaks open requests and hides existing templates, so leavers and role changes need planning.
Connected user considerationsNo proposal building
The integration signs documents you already have. There is no editor for building a branded proposal or quote inside Salesforce, so pricing tables and content come from another tool or a static PDF.
Dropbox Sign Salesforce pageText tags are one line, fixed height
The physical length of the tag sets the field width, height cannot be set, tags must sit on one line, and a tag for a signer who was not added simply does not appear.
Text tags in SalesforceNo tablet or mobile authoring
Dropbox states the integration “doesn’t support iPad, tablet, or other mobile devices” for creating templates or requesting signatures. Merge fields are limited to eligible field types, and SMS delivery needs an API-plan add-on.
RequirementsConnected to Salesforce versus built inside it.
Fair note: Dropbox Sign is simple, well priced and reliable for getting a signature on a finished document, and for teams that already live in Dropbox it fits naturally. This page is about the specific case of a sales team that wants proposals, quotes and signatures to live on the Salesforce record.
What changes when signing runs inside Salesforce.
Build the document, not just sign it
SalesSign installs as a managed package and runs through Salesforce Canvas and Lightning Web Components. A rep opens an Opportunity, Quote, Account or custom object, launches the builder and the proposal is created, edited, sent, tracked and signed without leaving the page. Fixed contracts can be uploaded as PDFs with fields placed visually.
Templates that belong to the team
Templates are built once, version-controlled and shared across the account. Merge fields follow lookups up to five relationships deep and pull related lists into tables. When a layout changes, you edit the template; there are no text tags to re-place and no single connected user whose departure locks everything.
Signed PDF, status and engagement on the record
Every send, view, signature and the final PDF land on the Salesforce record as they happen, ready for reports and Flows. Tracking sessions show which pages each recipient read and for how long, so reps know which deals are live before they follow up.
Dropbox Sign and Salesforce, answered.
What are the requirements for Dropbox Sign for Salesforce?
A Dropbox Sign Standard or Premium team with Salesforce enabled (a free account gets a 30-day trial), a connected user with the admin or developer role in Dropbox Sign and ideally the System Administrator profile in Salesforce, matching email addresses in both systems, and permission to add fields and buttons to objects and layouts. The integration does not support template creation or sending from iPads, tablets or phones.
Can I use my existing Dropbox Sign templates in Salesforce?
No. Templates created in the Dropbox Sign app or through the API cannot be used from Salesforce. They have to be recreated in Salesforce, and from then on edited only there. Templates created in Salesforce can be used in the app and the API.
How do text tags work in Dropbox Sign for Salesforce?
A text tag is written into the source document in the form [Type|Required|Signer|Label|ID], for example [sig|req|signer1]. Dropbox Sign scans the file automatically when it is sent from Salesforce and replaces each tag with a field. Tags must be on one line, the tag’s length sets the field width, and if the template uses tags the file source must be File Attached to Record.
Is there a free Dropbox Sign for Salesforce trial?
Yes. Installing the package with a free Dropbox Sign account enrols you in a 30-day trial. After that the integration needs a paid Standard or Premium team with Salesforce enabled.
Which Salesforce objects does Dropbox Sign support?
Accounts, Contacts, Leads and Opportunities out of the box. Any other standard or custom object can be added by creating a lookup field, a Visualforce page, a custom button and a permission set entry, then registering the object in the Dropbox Sign settings.
What is the Salesforce-native alternative to Dropbox Sign for Salesforce?
SalesSign runs the proposal builder, e-signature and engagement tracking inside Salesforce through Canvas and Lightning Web Components, with visual field placement, versioned team templates and real-time write-back. Plans start at £19 per user per month with a 14-day free trial. See SalesSign vs Dropbox Sign.
See proposals built, sent and signed without leaving Salesforce.
A 20-minute live demo on a real Opportunity, mapped to how your team sells. Or start a 14-day free trial from the pricing page.