Options reference
Every option of a sending template (eSignature) and of a Gen template, grouped by editor tab. For the step-by-step, see Create a template and TrueSign Gen.
Sending template (eSignature)
Documents
| Option | Effect |
|---|---|
| Document title | The name the signer will see. Accepts merge fields — Contract {{Account.Name}} |
| Attach source record documents | Automatically attaches the source record's files to the send, with no manual selection |
| Document filter | Restricts that automatic attachment to matching files (by name, by type) |
| Mention fields | Informational text zones placed on the document |
Recipients
| Option | Effect |
|---|---|
| Resolve signers from the record | Recipients are derived from the contacts linked to the source record, with no typing |
| Lookup field path | States which lookup field designates the recipient (e.g. an opportunity's primary contact) |
| Sender is signer | The user who sends also signs, with a signing link embedded in Salesforce |
| Designated sender | Requests go out on behalf of this user, whoever triggers the send — essential for automated sending |
Each recipient's role (signer, approver, in copy), authentication, language, message and private note are set recipient by recipient.
Signature
| Option | Effect |
|---|---|
| Provider | Yousign or weSign for this template — blank = org default. See Providers |
| Signature level | SES · AES · QES — see Levels |
| Authentication mode | Email OTP, SMS OTP, access code — overridable per recipient |
| Signing mode | Sequential (one after another) or simultaneous |
| Brand | Visual identity applied to weSign pages and emails (logo, colours) |
Deadlines and reminders
| Option | Effect |
|---|---|
| Expiration (days) | From 1 to 365 — 30 by default |
| Expiry warning (days) | Warning email N days before the deadline |
| Enable reminders | Automatic chasing of signers who have not signed |
| First reminder after (days) / Frequency (days) | The chasing rhythm |
| Maximum number of reminders | A cap, so as not to harass |
Approval
See Approval workflow for how it works.
| Option | Effect |
|---|---|
| Require internal approval | Turns on the workflow: nothing goes out before validation |
| Internal approver 1 / 2 / 3 | The sequential chain, up to 3 levels |
| Approval reminder (days) | Chases the current level's approver |
| Escalation (days) | Delay before automatic escalation |
| Escalation target | The approver's manager, the next level, or a named user |
Sending experience
| Option | Effect |
|---|---|
| Quick Send | Direct send, no preview screen |
| Embedded in Salesforce | The sending interface opens in the page, not in a new tab |
| Sending experience | Standard, Quick Send or embedded |
| Show: Send button / Fields button / email subject / email message / remind-expire / Chatter | Fine control over what the sender sees — and therefore what they can change |
| Sender permissions | What a non-administrator sender is allowed to change before sending |
Locking a template down
Unticking the "Show…" options is how you freeze a template: the sender sends, but cannot change the email subject, the deadlines or the recipients. That is what lets you hand a legal template to a sales team.
Lifecycle and scope
| Option | Effect |
|---|---|
| Target object | The Salesforce object this template is offered from |
| Template type | Standard envelope, tied to a generation, or pre-fill only |
| Active | Offered to users |
| Draft | Visible to administrators only; cannot be triggered by a button or Flow |
| Enable for bulk send | Makes the template selectable in Bulk send. A document then becomes mandatory |
After signing
| Option | Effect |
|---|---|
| Write the signed document back | The signed PDF returns to the record's files (enabled by default) |
| Notifications | Which events notify the sender: send, each signature, completion, expiry, decline |
| Custom fields | Metadata attached to the envelope (internal reference, project code) — invisible in the document, useful in reports |
| Advanced options | Fine-tuning of the signing journey |
Writeback and merge fields are configured in their own tabs.
Gen template (document generation)
| Option | Effect |
|---|---|
| Source object | The Salesforce object generations start from — final |
| Document | The Word file (.docx) carrying the tags |
| File name | Accepts merge tags — Quote {{Account.Name}} |
| Suffix | Appended to the name: date, source object name, or both |
| Currency locale | Amount formatting for this template |
| Destination | Record files, library, or both |
| Library name | If the destination includes a library |
| Linked envelope template | To chain generation → signature |
| Automatic launch | Generation fires on click, no intermediate screen |
| Preview before send | The user checks the resolved document before confirming |
| Send for signature | Untick to produce the document only, with no signing |
| Active | A real circuit breaker: an inactive template does not generate, even when called by a Flow |
| Description | Internal help, invisible to the recipient |
Related lists (alias, filter, sort, cap) and the tag syntax are described in TrueSign Gen.
Generate + sign in one click
Combine linked envelope template + automatic launch + send for signature: the user clicks once, the document is built and goes out for signature.