OneSpan Sign for Salesforce


This is the QuickStart Guide for OneSpan Sign for Salesforce. It is intended for Salesforce System Administrators who want a quick way to install and explore the product for the first time.

This guide describes:

Installing the Solution


  • You are a Salesforce System Administrator, and have a Salesforce Sandbox account (on
  • If you want, you can evaluate the application using a Salesforce Developer account or a Salesforce Professional account.

  • The OneSpan Sign Administrator must have a Salesforce System Administrator profile, and the OneSpan Sign username and Salesforce email address must be the same.
  • Chatter is enabled in Salesforce.
  • You have an OneSpan Sign Sandbox account. If you don't yet have an account, you can sign up for one.
  • You have one of the following Salesforce Editions:
    • Professional
    • Enterprise
    • Unlimited
    • Developer


To install OneSpan Sign for Salesforce for the first time:

  1. Open a web browser, and navigate to
  2. Using the search field at the top of the page, search for OneSpan Sign.
  3. Click the OneSpan Sign for Salesforce app, and then click Get It Now.
  4. Click Log in to the App Exchange, and enter your Salesforce login credentials.
  5. Click Install in Sandbox. An Almost there! screen appears.
  6. Select the I have read and agree to the terms and conditions box.
  7. Click Confirm and Install.
  8. On the screen that appears, enter the username of your Salesforce Sandbox account. The Transaction Installation Details page appears.
  9. Click the Install for Admins option, and click Continue. An Approve Third-Party Access dialog box appears.
  10. Select the Yes, grant access to these third party web sites box, and click Continue.
  11. If you have a Production Salesforce installation:
    1. Review the displayed information, and click Next. A Choose security level page appears.
    2. Select Grant Access to Admins Only, and click Next. An Install Transaction page appears.
    3. Click Install.
    4. After the installation is complete, click Manage Licenses, and assign the Salesforce license to the user who wants to use OneSpan Sign for Salesforce.

      Because you are installing the application for the first time, you have only one Salesforce license. For additional licenses, contact your OneSpan Sign CSR (Customer Satisfaction Representative).

  12. The OneSpan Sign Installed Transaction Details page appears, enabling you to review the application details.

Configuring the Solution

This section describes the following aspects of configuring the solution:

Configuration Prerequisites

  • You are both a Salesforce System Administrator and an OneSpan Sign Administrator.
  • Your Salesforce Sandbox account is configured with a First Name, Last Name, and Email Address. These values are the same as those used for your OneSpan Sign Sandbox account.

Connecting to OneSpan Sign

OneSpan Sign for Salesforce must be connected to your OneSpan Sign Sandbox account.

To connect OneSpan Sign for Salesforce to your OneSpan Sign Sandbox account:

  1. Log in to the relevant organization as a System Administrator.
  2. Click the App Menu in the top-right corner. From the drop-down menu, select OneSpan Sign. The OneSpan Sign Transactions Home page appears.
  3. Click the Admin tab. The OneSpan Sign Admin page appears.
  4. In the Connection Settings section of the Configuration tab, select your environment from the Environment drop-down menu. For more information on environments, see Intro.
  5. Choose either Admin Credentials or OneSpan Sign API Key as the Connection Method. Then type your OneSpan Sign username andOneSpan Sign password in the text fields.
  6. Click Connect. A dialog box requests the permission to connect.
  7. Click Allow. A connection is established between OneSpan Sign for Salesforce and your Sandbox OneSpan Sign account.

Configuring an Existing Salesforce User

To enable an existing Salesforce user to access OneSpan Sign for Salesforce:

  1. Log in to the relevant organization as a System Administrator.
  2. In the top menu, click Setup.
  3. In the Administer section, select Manage Users.
  4. Click Users.
  5. Click the name of the Salesforce user.
  6. Click Permission Set Assignments, and then click Edit Assignments. In the Permission Set Assignments page, set the permissions.

    To view descriptions of the Permission Sets, click Configuring Permission Sets for 5.0. If you want to evaluate OneSpan Sign for Salesforce for the first time, select all the Permission Sets.

  7. Click Save.

Testing the Solution

After you've installed and configured your solution, you can test it by sequentially performing the following procedures:

  1. Creating a Transaction
  2. Adding Documents
  3. Adding Recipients
  4. Preparing Documents
  5. Sending the Transaction
  6. Signing the Transaction

Creating a Transaction

To create a transaction:

  1. Log into OneSpan Sign for Salesforce as a user who has permission to create a transaction.
  2. On the OneSpan Sign for Salesforce menu, click Transactions. The Transactions Home page appears.
  3. In the Recent Viewed section, click New.
  4. Enter a Transaction Name.
  5. Click Next. The transaction is created, with the logged-in user as its default recipient.

Adding Documents

OneSpan Sign supports the following types of documents:

  • Adobe's Portable Document Format (*.pdf)
  • Microsoft Word (*.doc or *.docx)
  • Open Office (*.odt)
  • Text (.txt)
  • Rich Text Format (.rtf)

Please be aware of the following:

  • The maximum size of a single document is 16 MB. The only exceptions concern our Salesforce and Microsoft SharePoint connectors, whose maximum is 5 MB per document. Smaller documents yield better performance — we recommend under 5 MB per document.
  • If you enable email delivery while configuring a recipient, documents that are larger than 5 MB will not be added as attachments to the email.
  • OneSpan will not provide Technical Support for a transaction or transaction template that has more than 10 documents.
  • Document file names should not contain any of the following comma-separated characters: *, /, \, :, <, >, |, ?, ".
  • A document's name cannot contain the string esigned.
  • Uploading password-protected or corrupted documents will trigger an error.
  • PDFs added to a transaction must not have syntax errors. We strongly recommend that you scan a PDF for syntax errors before you add it to a transaction (e.g., by using Adobe's Preflight tool).
  • PDFs with the NeedAppearances flag set to true are not currently supported.

To add documents to your transaction:

  1. From the Documents section of the transaction, click Add Document. A new page appears.
  2. Click Upload local files.
  3. Click Choose Files.
  4. Click Add selected documents. The documents you selected are added to the transaction.

Adding Recipients

To add two recipients to your transaction:

  1. From the Recipients section of the transaction, click Add Recipient. A new row appears.
  2. From the drop-down menu in that row, select Contact.
  3. Click the magnifying glass next to the Lookup field, and select a Contact.
  4. Click Add Recipient again. A new row appears.
  5. From the drop-down menu in that row, select External Email.
  6. Manually enter the First Name, Last Name, and Email of a suitable recipient.
  7. Click Save Recipients. The two recipients you specified are added to your transaction.

Preparing Documents

To prepare your documents for signing:

  1. While viewing your transaction (to which one or more documents have been added), click Prepare.The Designer view appears.
  2. On the Electronic Disclosure and Signature Consent agreement, click the right-facing arrow to display the transaction's first document.
  3. From the Recipients menu, select a recipient.
  4. Click Fieldse to add a Signature Block for that recipient.
  5. Drag the Signature Block to where you want it to appear in the document.
  6. If you want to change the Signature Block type, or if you want to add a field, click the Settingsicon. The Signature Block menu appears.
  7. Repeat Steps 4-7 for each Signature Block you want to add to the document.
  8. If there is another document, click the right arrow to display it, and repeat Steps 4-8.
  9. Repeat the previous step for each document in the transaction.
  10. Close the window by clicking the X in the upper right corner.

Sending the Transaction

To send your transaction to be signed:

  • From the Transaction Edit page, click Send. The transaction is sent to be signed, and each recipient receives an appropriate email.

Signing the Transaction

To sign the documents in your transaction:

  1. If you are the Transaction Owner as well as a recipient (with at least one assigned Signature Block), on the Transaction Detail page, click Sign. A preview window displays the first document.
  2. If you are a recipient but not the Transaction Owner:
    1. In the email you received, click Go to Documents.
    2. Read the Consent Agreement, and click Accept. A preview window displays the first document.
  3. Sign all of your Signature Blocks in the document. Those blocks should be indicated by sticky notes.

    If any unsigned Signature Blocks lie outside your screen, an Unsigned Signatures notification displays the number of signatures that are still required. A progress bar at the top of the document indicates the number of signatures you have completed, as well as the total number of signatures assigned to you in this document (e.g., 3/10 completed).

  4. To confirm your signatures in the current document, click OK.
  5. Repeat Steps 3-4 for each document in the transaction.
  6. Once all your signatures have been applied, a refreshed version of the screen confirms that you have finished signing the transaction.

    Once a transaction has been signed by all recipients, its status is changed to Completed. To view that status, it may be helpful to refresh your page.

  7. To verify that all documents in a completed transaction have been signed, in the Documents section of the Transaction Detail page, click the icon under Signed Documents. This enables you to download your documents. Open each document, and verify that all its Signature Blocks have been signed.

To learn more about using OneSpan Sign for Salesforcev4, see the OneSpan Sign for Salesforce 4 User's Guide.

Was this information helpful?