A Salesforce eSignature app your admins can install, configure and roll out the same week

A managed package from AppExchange, a permission set for the people who send, and a button on the record. Then your team can send a contract for signature without leaving Salesforce.

Managed package from AppExchange INSTALLED Permission sets Senders Admins Opportunity Send for signature Test send sandbox first Live the same week no code, no consultants
Install and roll out

The Salesforce eSignature app: three admin sessions from AppExchange to first send.

Install the eSignature app from AppExchange into a sandbox, prove it on one object, then repeat the same steps in production.

Install the managed package from AppExchange, assign the SignSecure permission set to the users who send, and the Send for Signature button is live on any object you choose.

Session one

Install the managed package

Install from AppExchange into your sandbox, connect the org once, and let the package bring its objects, fields and Lightning actions with it. Upgrades arrive as package versions, so nothing you built gets touched.

Session two

Assign permission sets and map fields

Give the Senders permission set to the people who send and the Admins set to the people who configure. Map the merge fields going out and the status fields coming back.

Session three

Test, then repeat in production

Send a real document to yourself in the sandbox, watch the status fields move and the signed PDF file itself, then run the identical steps in production and hand it to the team.

An admin checklist that fits on one screen.

Everything below is standard Salesforce administration. If you can add a Lightning action to a page layout, you can finish this list.

Field mapping lets you merge Salesforce fields into a contract template, including account name, term, pricing and signer details, so the document arrives already filled in and the values write back when it is signed.

Before your first send

  • Install into sandboxManaged package, installed for the admins and senders you choose.
  • Connect the orgOne authorisation, done once, by an admin.
  • Assign permission setsSenders and Admins, assigned the way you assign any other set.
  • Add the action to layoutsOpportunity, Quote, Contract and any custom object you want it on.
  • Map fields both waysMerge fields out on send, status and signed values back on completion.
  • Set the filing rulesTarget record, Files location and the naming pattern for signed PDFs.
  • Send a sandbox testWatch the whole round trip before anyone else sees it.
  • Repeat in productionSame steps, same order, then tell the team the button is live.

See what the writeback does

eSignature app for Salesforce pricing, published in full.

The Salesforce app is included on every paid plan rather than saved for an upgrade tier. Here is the whole picture.

Free

For trying the whole round trip yourself.

$0forever

No card needed

  • Send documents for signature
  • Draw, type or upload a signature
  • Sealed PDFs with an audit trail
  • A place to test the signer experience
Start free

Enterprise

For orgs with procurement, security review and scale.

Customtalk to us

Priced to your org

  • Everything in Business
  • Salesforce app included
  • Advanced routing and template locking
  • Security review support
  • Named onboarding for your rollout
Talk to us

See everything in the electronic signature software

Questions

What admins ask before they install.

Do I need a developer to install the Salesforce app?
No. It is a managed package from AppExchange: install it, assign the SignSecure permission set, and add the Send for Signature button to whichever objects your team works from.
Can Salesforce data be merged into the document before sending?
Yes. Field mapping pulls account, contact, term and pricing values straight from the record into the template, so the document arrives complete and the rep is only confirming the signer.
Is this a managed package?
Yes. You install the eSignature managed package from AppExchange, and it brings its own namespace, objects, fields and Lightning actions. Updates arrive as new package versions, so your own configuration stays exactly as you left it.
Can we install it in a sandbox first?
That is the path we recommend. Install into a sandbox, connect the org, assign the permission sets, and send a real document to yourself so you can watch the status fields update and the signed PDF file itself. Then run the same steps in production.
How long does a rollout usually take?
The work splits into three admin sessions: install and connect, assign permission sets and map fields, then test and repeat in production. Teams that set aside those three sessions are sending from live records the same week.
Do signers need a Salesforce licence?
No. Your signer receives an email, opens the document in their browser on whatever device they have, and signs. The Salesforce side is only for the people in your org who send and manage requests.
Is the Salesforce app charged as an add-on?
It is included on every paid plan. Business is $12 per user per month billed annually, and Enterprise is priced to your org. The full breakdown is on the pricing page.
Which objects can we put the button on?
Lead, Contact, Account, Opportunity, Quote, Contract and any custom object your admins have built. Details of each are on the Salesforce hub.
Can we automate sending rather than clicking the button?
Yes. The package ships invocable actions so you can trigger the signature request from a Flow, no developer needed. See Salesforce Flow eSignature actions.
Where do signed documents live afterwards?
In Salesforce Files, linked to the record that sent the request, named with the pattern your admin chose, with the certificate of completion beside it.

Book the sandbox session, and you are live this week.

Free to start, no card needed. The Salesforce app is included the moment you go paid.