Create a template
An Envelope Template captures the whole configuration of a typical send — documents, signers, merge fields, options — so users send in two clicks, without configuration mistakes.
Create a template
In the TrueSign app: TrueSign Setup → eSignature → Templates → Create Template (or "Import from DocuSign", or "Duplicate an existing one").
Creation starts with a two-field modal:
- Name — the template name;
- Data Source — the associated Salesforce object (Opportunity, Account, Contact, custom object…). It determines the fields available for merges and the records the template will be offered from. This choice is final.
The editor then opens with 6 sequential tabs — each validated before the next:
1. Documents
Upload the template's document(s), or check "Attach documents from the Salesforce record" to automatically include the record's files at send time. A dynamic filter can select the right files (e.g. Title LIKE 'Contract%'). Multiple documents have a configurable display order.
2. Recipients
Define signers as roles (Signer 1, Signer 2…), resolved at send time from:
- the opportunity's contact roles (e.g. "Decision Maker" → Signer 1);
- a Contact/User lookup field on the source object;
- a signing group;
- manual user input.
Per signer: authentication (email/SMS OTP, access code), language, dedicated email subject/message, private note, in-person mode, CC recipient.
3. Merge Fields
The Salesforce data injected into the document — see Merge fields.
4. Place Fields
Positioning of signature zones and form fields — see Field placement.
5. Options
| Option | Effect |
|---|---|
| Expiration | 1–365 days (default 30), with a warning email N days before |
| Reminders | First reminder after N days, then every P days — can be disabled |
| Routing | Sequential or simultaneous |
| Quick Send | Direct send without preview screen |
| Experience | Standard, Quick Send or embedded in the page |
| Document writeback | The signed PDF is re-attached to the record (enabled by default) |
| Sender notifications | On send, on each signature, on completion, on expiration, on decline |
| Delegated sender | The template designates a fixed sending user: requests go out on their behalf, whoever is logged in — essential for automated sends (Flows, NBA) |
| Signature provider | Yousign or weSign for this template — blank = inherits the org default. See Signature providers |
| Internal approval | 1 to 3 approvers validate before anything is sent, with conditional routing, reminders and escalation — see Approval workflow |
| Chatter | Automatic posts on the record — disable it for bulk-send templates |
This is also where data writeback is configured — see TrueSign Connect.
6. Custom Button
Generate the send button tied to this template — see Custom buttons.
Lifecycle
- Draft (
IsDraft) — visible and testable by administrators only; cannot be triggered by a button or Flow. - Active — offered to users on records of the source object.
- Inactive (
IsActive = false) — removed from selectors without being deleted; send history is preserved.
The document title supports merge fields: Contract - {!Account.Name} - {!Opportunity.Name} produces an individualized name on every send.