---
title: "TurboSign Launches Reusable PDF Signature Templates"
description: "TurboSign now saves a PDF as a reusable signature template with signer roles, sent from TurboDocx or through the API, and saves signed PDFs and audit trails back to Salesforce records."
url: "https://www.turbodocx.com/newsroom/turbosign-reusable-signature-templates"
---

# TurboSign Adds Reusable PDF Signature Templates with Signer Roles, and Saves Signed PDFs Back to Salesforce

> Set up a document your team sends again and again once, with the roles that sign it, and send it from TurboDocx or from your own systems. For teams sending from Salesforce, the signed PDF and its audit trail now return to the record they came from.

Product Launch. October 20, 2026.

**Jupiter, FL - October 20, 2026** - TurboDocx today released reusable PDF signature templates for [TurboSign](https://www.turbodocx.com/products/turbosign.md). A team uploads a document it sends for signature over and over, such as an NDA or a master services agreement, sets up the roles that sign it once, and every send after that starts ready to sign. People send it from TurboDocx; systems send it through the TurboSign API. The same release finishes the round trip for teams that send from Salesforce: once the last signer finishes, the signed PDF and its audit trail are saved back to the Salesforce record.

## Set it up once, send it every time

Most signature requests are not new documents. They are the same NDA, the same order form, the same onboarding packet, sent to a different person. Until now, somebody had to add the signers and place every field again each time, and that is where the countersignature goes missing or the date lands on the wrong page.

Now a PDF can be uploaded as a signature template. Each kind of signer becomes a role, such as Client and Countersigner. A role can be someone new each send, the sender, or a specific person who signs every time, like your head of legal, who can still be swapped out for a single send. Fields are placed per role, and the signing order, email message, reminders, expiration and document name are saved with the template. The next person who sends it only enters who is signing this time. A document that was already sent once can be turned into a reusable template after the fact.

The article's figure shows a Mutual NDA saved as a PDF signature template with two roles that sign in order:

| Role | Who signs |
| --- | --- |
| Client | Someone new each send |
| Countersigner | A specific person: your head of legal |

The next send, from the app or from code, only says who the client is:

```js
recipients: [
  { role: "client", name: "Jane Doe", email: "jane@example.com" },
]
```

The client changes every time; the countersigner is saved with the template and can be swapped for a single send.

Word and PowerPoint templates can carry a saved signature setup too, so a template that generates a document can create it and send it for signature with the signers and fields already in place. Only administrators and contributors can change a template's setup; anyone who can send documents can use it.

The [reusable signature templates](https://www.turbodocx.com/reusable-signature-templates.md) page covers where templates fit, and the step-by-step guide is in the docs: [How to Use a PDF as a Signature Template](https://docs.turbodocx.com/docs/TurboSign/PDF-Signature-Templates) and [How to Save a Signature Setup on a Template](https://docs.turbodocx.com/docs/TurboSign/Signature-Setups-on-Templates).

## Send the same template from your own systems

Every role has a key made from its name, so *Client* becomes `client`. A system that sends the template names the role and the person, and the fields placed for that role come with it. Your code never has to know where a signature goes on the page, and the template's owner can move a field without anyone redeploying anything. That is how a contract leaves a CRM, a billing system or an internal tool with the same fields every time, and because it is a plain API call, it integrates with any system your team already runs. In Dev Mode, the template's page shows its template ID and role keys so a developer can start from there. See [Use it from code](https://docs.turbodocx.com/docs/TurboSign/PDF-Signature-Templates#use-it-from-code).

> "Most of what gets signed is the same document going to a new person," said Nicolas Fry, Founder & CEO of TurboDocx. "Templates with roles mean the setup is done once, by the person who knows the document, and then sales, operations or an automated system can send it without getting a field wrong."

## Signed PDFs land back on the Salesforce record

Teams using TurboSign for Salesforce send documents for signature straight from a record. With this release, when the last signer finishes, TurboDocx saves the signed PDF and the audit trail to that record's files, and can move a field you choose, for example the opportunity stage to Closed Won. Write-back uses your organization's Salesforce connection, which is included on the Pro and Enterprise plans, and needs TurboSign for Salesforce 1.1.0 or later.

TurboDocx also watches that connection now. It keeps it active on its own, and if it stops working, for example because a Salesforce admin revoked it, TurboDocx emails your organization's admins and shows a Reconnect Salesforce message in the Salesforce settings. Reconnecting is safe: the current connection keeps working until the new one succeeds, and signed files that could not be saved while it was down still arrive if you reconnect within about a day. Setup is covered in the [Salesforce integration guide](https://docs.turbodocx.com/docs/Integrations/SalesForce).

## Building on the October identity release

Two weeks ago TurboSign added [per-signer identity verification](https://www.turbodocx.com/electronic-signature-identity-verification.md), with email or SMS passcodes or your own identity provider, and [embedded signing](https://www.turbodocx.com/embed-electronic-signature.md) inside your own app. A saved signature setup keeps each signer's verification choice, and every signed document is tamper-proof, with an audit trail on every signature. Details are in the docs for [identity verification](https://docs.turbodocx.com/docs/TurboSign/identity-verification) and [embedded signing](https://docs.turbodocx.com/docs/TurboSign/embedded-signing).

## Availability

PDF signature templates, saved signature setups and sending by role are available now in TurboSign. TurboSign's free plan includes 5 documents a month.

[Explore TurboSign](https://www.turbodocx.com/products/turbosign.md)

## About TurboDocx

TurboDocx provides e-signatures, quoting, and AI-enhanced document automation for teams that produce customer-facing documents at scale. The platform helps organizations eliminate manual document work while maintaining consistency, accuracy, and brand standards.

For more information, visit [TurboDocx.com](https://www.turbodocx.com/index.md) or contact IR@TurboDocx.com.

**Media Contact:** IR@TurboDocx.com