Seconds 1 to 5
Press send on the record
The send button sits on the Opportunity page layout. One press opens the template picker with your NDA at the top, because it is the one this team reaches for most.
NDA eSignature
Send an NDA from Salesforce and get it back on the record
Send an NDA from Salesforce without leaving the opportunity you are working. Open the record, pick the NDA template, and the counterparty name, entity and effective date arrive already merged. Your signer signs in a browser, your side countersigns, and the executed NDA files itself back where legal can find it.
Send an NDA from Salesforce in fifteen seconds
Three moves on a record your rep already has open. Nothing to download, nothing to retype.
Seconds 6 to 11
Fields arrive already merged
Counterparty name, registered entity, address, effective date and term all pull from the record. Your rep reads them rather than typing them, which is where the typos used to come from.
Seconds 12 to 15
Choose the routing and go
Pick mutual or one way, confirm the signer email that came off the contact, and press send. The NDA is in their inbox before your rep switches tabs.
The merge fields an NDA actually needs
Map these once on the template and every future NDA opens complete. Anything your org already stores can be added alongside them.
| Merge field | Source | What it fills |
|---|---|---|
| {!Account.Name} | Account | The trading name in the opening paragraph and the signature block. |
| {!Account.Legal_Entity__c} | Account | The registered entity that is actually bound, where it differs from the trading name. |
| {!Account.BillingAddress} | Account | The notice address, so notices go somewhere real. |
| {!Contact.Name} | Contact | The named signatory printed under the signature line. |
| {!Contact.Title} | Contact | The capacity they sign in, which is the part legal checks first. |
| {!Contact.Email} | Contact | Where the signing link goes and where reminders follow. |
| {!TODAY} | System | The effective date, unless the record carries its own. |
| {!Opportunity.NDA_Term__c} | Opportunity | The confidentiality period, so a two year and a five year NDA come off one template. |
| {!Opportunity.Owner.Name} | Opportunity | The countersigner named on your side of the agreement. |
Mutual or one way, and who countersigns
Both shapes come off the same template. What changes is the routing order and which signature blocks are switched on, and you set that once when you save the template.
- MutualTwo signature blocks, both parties bound. Counterparty signs first, your signer countersigns.
- One wayA single disclosing party block. The recipient signs and the document completes there.
- Routing orderSequential by default, so the countersigner is only asked once the other side has signed.
- Standing countersignerName a person or a role on the template so nobody has to remember who signs for your side.
- Reminders on both legsNudges run on your schedule for the counterparty and for the countersignature.
- Visible progressSigner status shows on the record, so anyone can see which leg it is waiting on.
After signature
Where the executed NDA lands, and how legal gets it back
The point of sending from the record is that the finished document comes home to it. Six months later, retrieval is a search rather than an email thread.
Attached to the record it came from
The sealed PDF posts to Files on the same Opportunity, Account or custom object the send started from, named so it reads clearly in a list. The certificate of completion is stored alongside it, carrying signer identity, timestamps and the full event history. Nobody files anything by hand, so nothing gets filed to the wrong place.
Findable by search
Because the file lives on the record, global search, list views and reports all reach it with the tools your team already uses.
Dates written back
Signed date and status write to fields on the record, so an NDA expiry report is a report rather than a spreadsheet.
Your sharing rules apply
Access follows the record. If someone can see the Account, they can see the NDA on it, and if they cannot, they cannot.
Exportable at any time
Legal can pull the sealed PDF and its certificate together whenever an audit, a diligence request or a dispute asks for them.
Valid on its own
The seal validates outside Salesforce too, aligned with ESIGN, UETA and eIDAS. See the legality page.
Send your NDA from the record today
Start free, map the template once, and the next NDA leaves in fifteen seconds. Seats are $12 per user per month on annual billing.