Box Sign Templates help organizations standardize recurring signature workflows in Salesforce by allowing administrators to import and configure reusable Box Sign templates. Instead of manually selecting documents, recipients, signing order, and email settings for every signature request, users can simply select a Box Sign Template when sending a request. The template automatically applies its predefined configuration, helping reduce manual work while ensuring consistency across common business processes.
Typical use cases include:
- Non-disclosure agreements (NDAs)
- Sales contracts
- Customer onboarding documents
- Employment agreements
- Procurement approvals
- Internal policy acknowledgements
Once a signature request is sent, it is tracked in Salesforce just like any other Box Sign request.
Using Box Sign Templates in Box for Salesforce
1.Import the templates
Salesforce administrators can import Box Sign Templates from Box into Salesforce.
Note: The Sign Template must already be created and existing in Box.
To import templates:
- Open the Box Sign Templates tab in Salesforce.
- Click Import Templates.
- Select one or more Box Sign Templates from your Box enterprise.
- Click Import Selected.
The selected templates become available for users when creating Box Sign requests.
2.Configure Template Settings
After importing a template, administrators can review and configure settings that determine how the template behaves in Salesforce by navigating to Box Sign Templates and choosing the template you’d like to edit. In Box Sign Templates you will see the list of all Sign templates you’ve already imported into your Salesforce instance.
Template configuration includes:
- Prefill field mappings
- Placeholder signer mappings
- Salesforce object mappings
These settings help reduce manual data entry by automatically populating document fields and recipient information using Salesforce data whenever possible.
3.Send a Signature Request Using a Box Sign Template
If Box Sign Templates have been configured for your organization by admins (see steps 1-2 above), you can use them when creating a new signature request.
To send a request:
- Open the Send Box Sign dialog.
- Select Box Sign Template.
- Choose the template you want to use.
- Review the automatically populated information.
- Complete any required placeholder recipients.
- Click Send or Preview & Send.
Once submitted, the signature request is processed through Box Sign and tracked in Salesforce like any other signature request.
Working with Placeholder Recipients
Some templates contain predefined recipients, while others include placeholder recipients that are completed when the signature request is created.
When you select a template containing placeholders, Box for Salesforce prompts you to provide the required signer information before sending the request.
Depending on your organization's configuration, some placeholder recipients may be automatically populated from Salesforce record data.
Locked Template Settings
Box Sign Templates can define which settings users are allowed to modify before sending a signature request. Depending on how the template was configured in Box, you may not be able to edit:
- Recipients
- Email subject
- Email message
- Signing options
- Documents included in the request
Locked settings help organizations maintain standardized signing workflows and reduce the risk of accidental changes.
Using Templates with Salesforce Flow
Box Sign Templates can also be used in Salesforce Flow. Instead of specifying one or more files when creating a signature request, administrators can configure Flow to reference an imported Box Sign Template. This approach is ideal for automating recurring processes such as customer onboarding, contract approvals, employee onboarding, and procurement workflows. If a template includes placeholder recipients, the Flow must provide the required recipient information before the request is sent.
Apex action "Send Box Sign Request
Add to the existing input table:
Input |
Type |
Required |
Description |
|---|---|---|---|
| Template Id | Text | No | A Box Sign template UUID or the Salesforce Sign_Template__c record Id. When set, the request is created from the template. |
| Files | No (This is a change) |
New screen-flow component: BoxSign Flow
The BoxSign Flow Lightning component can be placed on a Flow screen to let a user pick a template and send interactively.
Property |
Type |
Description |
|---|---|---|
| recordId | Text | Salesforce record the request is associated with |
| Object API Name | Text | API name of that record's object |
| Pre-selected Sign Template Id | Text |
Sign_Template__c record Id to open with the template already chosen |
| Pre-selected Box Template Id | Text | Box template UUID to open with the template already chosen |
Tracking Signature Requests
After a signature request is sent, it is tracked in Salesforce using the same Box Sign records and related lists as standard signature requests. Users can monitor the request throughout the signing process and review its status from the Box Sign homepage or within Salesforce.
Best Practices
To get the most value from Box Sign Templates:
- Create templates for documents that are sent frequently.
- Configure prefill field mappings to reduce manual data entry.
- Configure placeholder signer mappings whenever recipient information can be derived from Salesforce records.
- Lock template settings when consistent signing workflows are required.
Learn more