SIGN Butler V2 – Security Settings for Sign Requests

Sign Butler now supports additional security methods that can be applied when recipients access documents for signing.

These security options provide an extra layer of protection for documents containing sensitive or confidential information.

In this guide, you’ll learn about the available security methods and how to configure them.

Available Security Options #

The following security settings are available for each signer:

• Default – No additional verification required
• Password – Requires the signer to enter a password before accessing the document
• SMS Verification – Requires the signer to verify their identity using a code sent via SMS

Each signer can have a different security method configured.

Password Security #

Password security requires the signer to enter a predefined password before viewing the document.

Configuration Steps #

1. Navigate to Sign Request Templates.
2. Create a new Sign Request Template.
3. Complete the required information on the first page and click Next.
4. On the Signer Configuration page, locate the Security Settings dropdown.
   
5. Select Password.
6. A new Password field will appear in the Data Source mapping section.
   

7. Select the Data Source field that will provide the password value.
   – Any value from the Data Source can be used as password
   

8. Add the Signer to the request.

9. Send a document for signature.

Signer Experience #

1. The signer opens the Sign Request.
2. A Password Required screen is displayed.
   
3. The signer enters the password and click Submit.
   
4. After successful validation, the document becomes available for review and signing.

• If an incorrect password is entered, an Invalid Password message is displayed.
  
• After 3 consecutive failed attempts, the signer is temporarily blocked from further attempts for 10 minutes.
  

SMS Verification Security #

SMS verification requires the signer to enter a one-time verification code sent to their mobile phone.

Configuration Steps #

1. Navigate to Sign Request Templates.
2. Create a new Sign Request Template.
3. Complete the required information on the first page and click Next.
4. On the Signer Configuration page, locate the Security Settings dropdown.
5. Select SMS.
6. A new Mobile field will appear in the Data Source mapping section.
   
7. Map the field containing the recipient’s mobile phone number.
8. Save the template.
9. Send a document for signature.

Signer Experience #

1. The signer opens the Sign Request.
2. A Verification Code Required screen is displayed.
3. The last three digits of the configured phone number are shown for confirmation.
4. The signer clicks Send Verification Code.
   
5. A one-time verification code is sent via SMS.
6. The signer enters the verification code.
7. After successful validation, the document becomes available for review and signing.

• If an incorrect verification code is entered, an Invalid Verification Code message is displayed.
• After 3 consecutive failed attempts, the signer is temporarily blocked from further attempts for 10 minutes.

Default Security #

When Default is selected, no additional verification is required.

The signer can access the document directly through the Sign Request link and proceed with the signing process.

Configuration Steps #

1. Navigate to Sign Request Templates.
2. Create or edit a template.
3. On the Signer Configuration page, leave Security Settings set to Default.
4. Save the template.

No additional setup is required.

Combining Security Methods #

Different signers within the same Sign Request can use different security methods.

For example:

This allows organizations to apply stronger verification only where necessary.

Configuration Steps #

1. Navigate to Sign Request Templates.
2. Create a new template.
3. Configure two or more signer Data Sources.
4. On the Signer Configuration page:
   • Select the first signer Data Source.
   • Choose the desired security method (Default, Password, or SMS).
   • Add the signer.
5. Repeat the process for all additional signers.
6. Save the template.

Each signer will receive the same document but will experience the security verification configured specifically for them.

Examples:

• Signer 1 may be required to enter a password.
• Signer 2 may be required to verify via SMS.
• Signer 3 may access the document directly without additional verification.