Template Configuration
Templates are the foundation of a consistent signing experience. A well-configured template eliminates repetitive setup for senders and ensures every transaction goes out correctly - with the right documents, the right recipients, the right fields in the right places, and the right behavior configured from the start.
The Templates List
Navigate to to access the template library.
The list displays all templates in your account with four columns:
| Column | Description |
|---|---|
| Template Name | The name of the template. Click to open and edit. |
| Documents | The document(s) pre-attached to the template. Shows -- if no document is attached - this is valid; documents can be added at the transaction level instead. |
| Last Updated | The date the template was last modified. |
| Expiry Date | If a fixed expiry date is set on the template, it displays here. Blank if set to unlimited or expiry is defined in days. |
The three-dot menu next to each template offers a Delete option.
Use the filter icon next to the search bar to filter the list by template properties.
Create a new Template
Click Create New Template to open the creation dialog. Enter:
Template Name (required) - this appears in the template list and is what senders see when selecting a template. Use a name that clearly describes the use case (e.g., "NDA - Single Signer" rather than "Template 1").
Description (optional) - appears in the template details for reference.
Enforce Document Accessibility - when enabled, automatically extracts fields from uploaded documents tagged for accessibility to ensure the signing experience meets accessibility standards. This setting cannot be changed after the template is created. Decide before saving.
Click Save to create the template and open the template editor.
Template Editor Overview
The template editor has two stages accessed via the Next button in the top right:
Stage 1: Template Setup - configure documents, recipients, template details, and settings
Stage 2: Document Editor - place signing fields on the document for each recipient
The Template ID is displayed at the bottom of the editor at all times. This is the value used in the templateid button parameter when launching transactions from Salesforce - copy it before leaving the editor.
Stage 1: Documents
Template Documents
Upload one or more documents that will be pre-attached to every transaction created from this template. Use the Drag & drop files to upload area or click Add Document to browse.
Uploaded documents are numbered in order. The three-dot menu next to each document offers:
Change the display name of the document
Preview - preview the selected document's contents
Delete - remove the document from the template
Templates without pre-attached documents are valid. If your document is generated dynamically (for example, by Conga Composer), leave the Template Documents section empty and the document will be attached at the transaction level when the button is clicked.
Supporting Documents
Supporting documents are reference materials a recipient may need during signing - they are not signed. Click Attach Documents to add them. Supporting documents are delivered to recipients alongside the signing documents but contain no signature fields.
Stage 1: Recipients
Recipients in a template define who signs - either as named individuals, placeholders to be filled at send time, or the sender themselves. The settings available for each recipient vary by type.
Adding a Recipient
Click Add Recipient to add a new recipient row. Clicking the profile icon, a dropdown appears with three recipient type options:
| Type | Description |
|---|---|
| Recipient | A specific named person whose details (First Name, Last Name, Email, Title, Company, Language, Role) are defined in the template. Every transaction created from this template goes to this person. Useful for known counterparties or internal approvers who are always the same. |
| Placeholder | The recipient is defined at transaction time. Only a placeholder name (e.g., Signer1) is set in the template - the actual signer's details are supplied when the transaction is created. This is the most common type for Salesforce-launched transactions where recipient details come from the record. |
| Myself | Adds the sender as a recipient using their Sign account details. The Role is set to Owner and the sender's name, email, title, and company are pre-populated. Useful when the sender also needs to sign as part of the transaction. |
Recipient Settings - Available Tabs by Type
The three-dot menu on any recipient row provides access to their settings. The options available - and the tabs within the settings panel - differ by recipient type:
Placeholder recipients - three-dot menu offers: Edit Details, Add Attachments Request, Advanced Settings, Move Up/Down, Remove. Settings panel tabs: Recipient, Attachments, Advanced
Recipient type recipients - three-dot menu offers: Edit Details, Edit Notification Method, Add Authentication Method, Add Attachments Request, Advanced Settings, Move Up/Down, Remove. Settings panel tabs: Recipient, Notification Method, Authentication, Attachments, Advanced
Myself recipients - three-dot menu offers: Edit Details, Edit Notification Method, Move Up/Down, Remove. Settings panel tabs: Recipient, Notification Method
Recipient Tab
For Placeholder type: Set or update the placeholder name (e.g., Signer1, Signer2). This name is used when placing fields in the document editor and is what senders reference when filling in actual signer details.
For Recipient type: Enter or update the recipient's details:
| Field | Description |
|---|---|
| Type | The recipient type - Recipient (shown here), or can be changed to Placeholder. |
| Role | A label for this recipient's signing role (e.g., Signer1, Approver). Appears in the document editor when placing fields. |
| First Name / Last Name | The recipient's name. Required. |
| The recipient's email address. Required. | |
| Title | The recipient's title. Optional. |
| Company | The recipient's company. Optional. |
| Language | The language for this recipient's signing experience. |
For Myself type: Displays the sender's details (name, email, title, company) pre-populated from their Sign account. Role is set to Owner. These fields are read-only.
Notification Method Tab (Recipient and Myself types only)
Controls how the recipient is notified when it is their turn to sign.
| The recipient receives a signing invitation by email. This is on by default and is required - at least one notification method must be selected. | |
| SMS | The recipient also receives an SMS notification. Selecting this requires a mobile phone number to be configured on the Authentication tab. Requires enablement by Conga Support and is an additional purchase. |
Authentication Tab (Recipient type only)
Sets an additional identity verification step the recipient must complete before they can access the signing ceremony. The Type is General for standard recipients.
| Method | Description |
|---|---|
| None (Default) | No additional authentication. The recipient's identity is verified by their secure email login - they access the signing ceremony via the link in their invitation email. |
| SMS | A one-time SMS code is sent to the recipient's mobile phone number. The recipient must enter this code before signing. Requires a mobile phone number to be entered. Requires enablement by Conga Support and is an additional purchase. |
| Q&A | The recipient must correctly answer one or more challenge questions before signing. Questions and answers are defined here in the template. A minimum of one Q&A pair is required. Answer masking can be enabled so the answer is hidden when the recipient types it. |
| Q&A + SMS | Combines both Q&A and SMS authentication. The recipient must pass both checks before accessing the signing ceremony. Requires enablement by Conga Support and is an additional purchase. |
Attachments Tab (Recipient and Placeholder types)
Specify files the recipient must upload before they can complete signing. Enter a label describing what they need to provide (e.g., "Government-issued ID") and click Add to add more attachment requests. Recipients cannot complete signing until all required attachments are uploaded.
Advanced Tab (Recipient and Placeholder types)
| Advanced Tab | Recipient and Placeholder types |
|---|---|
| Personal Message | A custom message included in this recipient's signing invitation email, in addition to any message-to-all-recipients set in Template Details. Useful when different signers need different instructions. |
| Change Signer | Allows this recipient to reassign their signing role to someone else. When enabled, the recipient sees a delegation option during the signing ceremony. |
| Email Delivery | Delivers the signed documents to this recipient as an email attachment when the transaction completes. |
Recipient Signing Order
When multiple recipients are added, a Set signing order toggle appears above the recipient list. This toggle is off by default, meaning all recipients receive the transaction simultaneously.
When Set signing order is off: All recipients receive their signing invitation at the same time and can sign in any order.
When Set signing order is on: Each recipient is assigned a numbered position. Recipients sign in the order defined - the next recipient in the sequence only receives their invitation once all recipients at the previous position have completed signing.
A number appears to the left of each recipient row indicating their position in the signing sequence.
Grouping Recipients for Simultaneous Signing
With three or more recipients, you can combine sequential and simultaneous signing by assigning multiple recipients to the same position number. Recipients sharing the same number receive the transaction at the same time and can sign in any order relative to each other - but the next group in the sequence won't receive their invitation until everyone in the current group has completed signing.
To group recipients:
Enable the Set signing order toggle.
Click the position number to the left of a recipient row - it becomes editable.
Change the number to match another recipient's position to group them together.
Example: You have three recipients. Signer 1 and Signer 2 are both assigned position 1. Signer 3 is assigned position 2. Both Signer 1 and Signer 2 receive the transaction simultaneously. Once both have completed signing, Signer 3 receives their invitation.
This is useful for agreements requiring sign-off from multiple parties on one side before the document proceeds to the next party - for example, two internal approvers who can sign in parallel before the contract goes to the customer.
Signing order set in the template is the default but can be adjusted by the sender when creating a transaction. To prevent manual edits, send in background mode.
Template Details
Below the Recipients section, the Template Details panel contains the template name, an optional description, and an optional Message to all recipients - a single message that goes out to every recipient in their signing invitation email.
Share Template
The Share template toggle controls whether the template is available to all senders in your account or only to you. Enable this for any template intended for organization-wide use.
Signing Type
The Signing Type dropdown sets the default transaction type for all transactions created from this template.
| Signing Type | Description |
|---|---|
| eSigning | Standard electronic signing. Recipients sign remotely via email invitation. This is the default and most common option. |
| In-Person eSigning | The signing ceremony is conducted in person on a shared device. The sender hosts the session and each recipient signs in turn. |
| Virtual Room | A hosted virtual signing session where the sender and recipients can be present simultaneously in a guided signing experience. |
| In-Person Electronic Notarization | A notarization workflow conducted in person with a commissioned notary. Requires enablement by Conga Support and is an additional purchase. |
| Remote Online Notarization | A notarization workflow conducted remotely via audio-visual technology with a commissioned notary. Requires enablement by Conga Support and is an additional purchase. |
Click Configure next to the signing type dropdown to access additional configuration options specific to the selected type.
In-Person Electronic Notarization and Remote Online Notarization will not appear unless enabled by Conga Support. Contact your Conga account team if your organization requires notarization workflows.
Settings Panel
Click the Settings gear button to expand the full settings panel. These settings control the behavior of every transaction created from this template. All of them can be overridden at the transaction level by senders unless otherwise noted.
Language and Timezone
| Setting | Description |
|---|---|
| Language | The default language for the signing experience presented to recipients. |
| Timezone | The timezone used for expiration date calculations and timestamp display. |
| Setting | Description |
|---|---|
| Enforce Document Accessibility | Grayed out after template creation - this was set when the template was first created and cannot be changed. Automatically extracts accessibility-tagged fields from uploaded documents. |
| Review Before Completion | Allows the transaction owner to review the transaction and its documents before marking it as complete. Useful when a final review step is required after all signers have signed. |
| Ad-hoc Cobrowsing | Allows creating a cobrowsing session between the Signer and the Sender. When enabled, the sender can initiate a live screen-sharing session to assist the signer in real time. |
| Signer Cobrowsing | Allows the Signer to create a help request for a cobrowsing session with the Sender. When enabled, the signer can request assistance from the sender during signing. |
Reminders
Click Configure to set template-level reminder defaults.
| Setting | Description |
|---|---|
| Enable Reminders | Turns on automatic reminder emails for this template's transactions. |
| Send reminder in (days) | How many days after sending the transaction the first reminder email goes out. |
| Repeat Reminder | Enables recurring reminders after the first. |
| Number of days | How many days between each repeated reminder. |
| Total Reminders | The total number of additional reminders to send (1–5). |
Expiration
Controls when transactions created from this template expire - how long signers have to complete signing before the transaction auto-expires.
| Setting | Description |
|---|---|
| Type: Day(s) | Expiration is set as a number of days from when the transaction is sent. Enter the number of days in the Days field. |
| Type: Date | Expiration is set as a specific fixed calendar date. All transactions created from this template expire on that date regardless of when they were sent. |
| Unlimited Expiration | When checked, transactions never expire. |
Using a fixed Date expiration type means all transactions from this template share the same expiry date. This is only appropriate for templates tied to a specific event or deadline. For ongoing use, choose Day(s) or Unlimited.
Uploads
| Setting | Description |
|---|---|
| Unlimited | When toggled on, recipients can upload any number of files per attachment. |
| Max number of files | When Unlimited is off, enter a value between 1 and 999 to cap the number of files per attachment. |
Field Formatting - Font Size
Sets the default font size for text displayed in signing fields on the document. Available sizes range from Auto-fit through 8px to 72px. Auto-fit scales the text to fill the field automatically, regardless of how much text is entered. Use a fixed size when you need consistent visual presentation across all fields.
The Document Editor
After clicking Next, the document editor opens. This is where you place signing fields onto the document for each recipient.
Editor Layout
The editor has three main areas:
Left panel - Recipients and Fields: Shows the recipient list at the top and the available field types below. Click a recipient to select them before placing fields - fields are always assigned to the currently selected recipient.
Center - Document canvas: The document displayed page by page. Click anywhere on the canvas to place the selected field type, or drag fields from the left panel onto the document.
Right panel - Field Settings: Appears when a field is selected on the canvas. Shows all configurable properties for that field.
Toolbar Icons (Top Right)
Five icons appear in the top-right toolbar of the document editor, to the left of the Done button:
| Icon | Name | Function |
|---|---|---|
| Keyboard | Keyboard Shortcuts | Opens a reference panel listing all keyboard shortcuts available in the editor. |
| Settings gear | Template Settings | Opens a dialog to edit the template's name, description, message to recipients, signing type, language, timezone, and all behavioral settings. This is the same settings content as Stage 1 but accessible without leaving the editor. |
| Page with down arrow | Save Layout | Saves the current field placement on the document as a named layout that can be reapplied later. |
| Page with up arrow | Apply Layout | Applies a previously saved layout to the current document, placing fields according to the saved configuration. |
| Eye | Document Visibility | Controls which recipients can see which documents in the transaction during the signing ceremony. |
Keyboard Shortcuts
Navigate:
Open keyboard shortcuts: ⌘ /
Go to the Recipients and Fields panel: ⌘ Shift F7
Go to the Document: ⌘ Shift F8
Go to the Documents and Fields Settings panel: ⌘ Shift F9
Field actions:
Select multiple fields: Shift + Click
Select all fields on the current page: ⌘ A
Copy field(s): ⌘ C
Paste field(s): ⌘ V
Delete field(s): Delete or Backspace
Save and Apply Layout
Layouts let you save a field placement configuration and reuse it across documents of the same type.
To save a layout: Click the Save Layout icon, enter a Name and optional Description, and toggle Share layout on if you want other senders to be able to apply it. Click Save.
- To apply a layout: Click the Apply Layout icon, optionally enable Show shared layouts to see layouts saved by others, select a layout from the dropdown, and click Apply. The saved field placements are applied to the current document.Note: Layouts are particularly useful when you regularly use the same document structure. Save a layout once from a well-configured template, then apply it when creating future templates with the same document rather than placing fields from scratch.
Document Visibility
Document Visibility controls which recipients can see which documents during the signing ceremony. This feature must be enabled in Feature Settings → Document Preparation before it is available. See Section 2.6.
To configure document visibility:
Click the Document Visibility (eye) icon in the toolbar.
Select the document you want to configure from the dropdown - each document in the template has its own visibility settings.
The dialog shows two groups:
User- recipients who are not required to sign this document. Check or uncheck each recipient to control whether they can see it.
Signers - recipients who have signing fields on this document. These cannot have visibility removed; they must be able to see any document they are required to sign.
Click Save.
Field Types
Select a recipient in the left panel, then drag or click a field type to place it on the document. Fields are always assigned to the currently selected recipient - switch recipients before placing fields intended for a different signer.
| Field | Description |
|---|---|
| Signature | The primary signature field. When clicked, the field settings panel shows a Signature Type option (see below). |
| Signer Initials | An initials field. Signers draw or type their initials. |
Signature Types (configured in the field settings panel after placing a Signature field):
| Type | Description |
|---|---|
| Click-to-Sign | The signer clicks to apply a pre-typed or pre-drawn signature. No additional drawing required. The simplest signing experience. |
| Hand-drawn | The signer draws their signature with a mouse, stylus, or finger. |
| Mobile Signature | The signer receives a link to open the document on their mobile device and draws their signature using their finger or a stylus. Requires the Mobile Signature feature to be enabled in Feature Settings. |
| Uploaded Image | The signer uploads an image of their signature. Requires the Signing via Uploaded Image feature to be enabled in Feature Settings. |
Signer Information Fields
These fields auto-populate with the signer's information after signing is complete. They do not require signer input.
| Field | Description |
|---|---|
| Signing Date | Auto-populated with the date the signer completed signing. |
| Signer Name | Auto-populated with the signer's full name. |
| Signer Title | Auto-populated with the signer's title (if provided in recipient details). |
| Signer Company | Auto-populated with the signer's company (if provided in recipient details). |
Input Fields
These fields require the signer to enter information during signing.
| Field | Description |
|---|---|
| Date Field | A date picker field. The signer selects a date. |
| Text Field | A single-line text input. Used for short text entries and for writeback tag values from Salesforce. |
| Text Area | A multi-line text input. Used for longer free-form entries. |
| Checkbox | A checkbox the signer can check or leave unchecked. Can be set as required. |
| Radio | A radio button group. Signers select one option from the group. |
| List | A dropdown list of options. Signers select one value. |
| Label Field | A read-only text label displayed on the document. Not an input - used to display static text to the signer within a field area. |
Field Settings Panel
Clicking any placed field opens the Field Settings panel on the right. Settings vary by field type but common properties include:
Signature Field Settings
| Setting | Description |
|---|---|
| Field Name | Auto-generated unique ID. Can be left as-is unless you are using this field for writeback, in which case paste the writeback tag value here. |
| Recipient | Which recipient this field belongs to. Change to reassign the field to a different signer. |
| Field Tooltip | Helper text shown to the signer when they hover over or interact with the field. |
| Signature Type | Click-to-Sign, Hand-drawn, Mobile Signature, or Uploaded Image. |
| Is Optional | When toggled on, the signer is not required to complete this signature field before finishing. Requires Optional Signatures to be enabled in Feature Settings. |
Text Field Settings
| Setting | Description |
|---|---|
| Field Name | For writeback, paste the writeback tag value from the Data Mapping Helper here. For pre-fill (insert field value from source), also use the tag value here. |
| Recipient | Which recipient this field is assigned to. |
| Field Tooltip | Helper text shown to the signer. |
| Default Value | Pre-populates the field with a value. For Salesforce pre-fill, this is handled via the Data Mapping Helper rather than the Default Value field. |
| Max Length | Maximum number of characters the signer can enter. Default is 3000. If using writeback to Salesforce, set this to 255 to match Salesforce's text field character limit - otherwise writeback will fail. |
| Is Required | Whether the signer must complete this field before finishing. |
The Layout panel below the Settings section lets you precisely control field position and size using pixel values for Top, Left, Width, and Height - useful when you need fields to align precisely with document elements.
Using the Data Mapping Helper
The Data Mapping Helper is accessible from the top-right toolbar in the document editor. It shows all configured data mappings and lets you copy the correct tag value to paste into a field's Field Name setting.
To use it:
Select your Target Source (e.g., Salesforce).
Select your Target Object (e.g., Opportunity).
The table shows all configured mappings for that object, with the Target Field, the Tag Used With column (indicating which field type to use - e.g., Text Field), and a Copy link.
Click Copy next to the field you want to map.
Close the Data Mapping Helper.
Click the signing tag on the canvas you want to map.
Paste the copied value into the Field Name field in the Settings panel.
Saving and the Template ID
The template editor saves automatically as you work - a Saved confirmation appears at the bottom of the canvas after each change. You do not need to manually save between field placements.
The Template ID is displayed at the bottom of the editor at all times. This is the value used in the templateid parameter when building Salesforce buttons (covered in Section 4.7). Copy it before navigating away from the template.
If you need the Template ID later and don't have it saved, navigate back to the template and it will be visible at the bottom of both Stage 1 and the document editor.
Previewing the Template
Click the eye icon in the top-right toolbar to preview the signing experience as a recipient would see it. This is useful for verifying field placement, checking that required fields are correctly marked, and confirming the overall layout before using the template in production transactions.
The preview shows the document with all fields rendered as they will appear to the signer for the currently selected recipient. Switch recipients in the left panel to preview each signer's view.
Common Template Configuration Mistakes
| Mistake | What Happens | How to Avoid |
|---|---|---|
| Not setting Max Length to 255 on writeback text fields | Writeback silently fails if the signer enters more than 255 characters | Always set Max Length to 255 on any field using a writeback tag |
| Pasting the writeback tag into Default Value instead of Field Name | The field is pre-filled with the tag string instead of mapping to Salesforce | Tag values always go in Field Name, not Default Value |
| Using a fixed Date expiration on a reusable template | All transactions expire on the same date regardless of when they're sent | Use Day(s) or Unlimited for templates intended for ongoing use |
| Setting Enforce Document Accessibility after template creation | Not possible - the setting is locked after creation | Decide at creation time; create a new template if the setting needs to change |
| Placing fields while the wrong recipient is selected | Fields are assigned to the wrong signer | Always verify which recipient is highlighted in the left panel before placing fields |
| Not sharing the template | Senders can't find or use it | Enable Share Template for any account-wide template |
