A transaction is the experience of a OneSpan Sign user as they review, accept, sign, and potentially download documents. The sender of a transaction generally performs the following procedures :
- Creating a Transaction
- Adding Documents to a Transaction
- Adding Recipients to a Transaction
- Configuring Recipient Authentication
- Adding Fields to a Document
- Managing Transaction Reminders
The Recipients section of the Draft page enables you to: (1) view all existing recipients of the transaction's signing invitations; (2) change various settings for those recipients; (3) add other recipients to the transaction.
This rest of this page describes the following procedures:
- Adding Recipients to a Transaction
- Changing a Recipient's Type
- Changing a Recipient's Personal Details
- Specifying the Signing Order
- Configuring Other Recipient Settings
- Removing a Recipient from a Transaction
- Sending Transaction Reminders
If you wish, you can also configure Authentication Methods for recipients.
Adding Recipients to a Transaction
Recipients can be added to a transaction that is in the state Draft or In Progress. If the transaction is In Progress, the signing process will be paused until changes are complete.
You may add up to a maximum of 100 recipients per template or transaction. However, for maximum performance we recommend that you limit the number of recipients to 20.
To add recipients to a transaction:
- Locate the transaction's Recipients section.
- Click Add Recipient. A new row appears for a new recipient.
- Type the First Name, Last Name, or Email of the recipient.
These three fields are to the right of the "recipient icon" (). Typing in any of those fields invokes a list of matching users from: (1) the recipients’ history; (2) the list of account senders. Complete each field either by typing, or by selecting an option from the recipient list that appears.You cannot use straight quotes ( " ) when entering a signer's name. However, you can use smart quotes ( ‘ and ’ ).
The following fields may appear for users in that list:
- First Name: The recipient's first name. This field is displayed only for the Recipient or Myself recipient types. It is a required field when you are defining a recipient who is one of those types.
- Last Name: The recipient's last name. This field is displayed only for the Recipient or Myself recipient types. It is a required field when you are defining a recipient who is one of those types.
- Email: The recipient's email address. This field must have the format of a valid email address. It is displayed only for the Recipient or Myself recipient types. It is a required field when you are defining a recipient who is one of those types.
- Repeat the above steps until you've added all desired recipients.
- Optional: To configure additional settings for a recipient (including recipient authentication), click the ellipsis beside the recipient (...), and then click Settings . These settings can be updated any time.
- Click Next to accept your settings. You can then add fields to the transaction's documents.
Undeliverable Email Policy
The following rules are applied to email addresses that fail to receive system notifications:
- If delivery to a recipient's email address fails more than three times: (1) that address is added to OneSpan Sign's blacklist; (2) the recipient will no longer receive OneSpan Sign emails.
- If a recipient's email becomes blacklisted from one account, it will be blacklisted from all OneSpan Sign accounts.
- If a transaction is sent that contains a blacklisted email address, an email will notify the transaction sender that the address has been blacklisted. A notification is sent each time the blacklisted address is used.
- If the transaction sender wants to remove an email address from the blacklist, they must contact their System Administrator, who must call our Support Team.
Supported Languages
If the list of supported languages has been limited the option to Use Transaction Language will appear on the recipient's Details page.
Enable this option will ensure that the recipient language always follows the transaction language. This means that if the transaction language is changed, recipients having this option enabled will inherit the new language.
Also, if enabled, the language will be set to the language of the transaction or template and the Language drop-down will be disabled.
If the option to Use Transaction Language is turned disabled, the language will remain as the transaction or template language, and the Language drop-down will be enabled.
Default behavior
When the use of supported languages has been limited, the following default behaviors will be in place:
-
When adding an external recipient, the Use Transaction Language option will be selected by default.
-
When adding a group recipient, the language (although not visible on the UI), will be set to Use Transaction Language. This means that any sender that accesses the signing ceremony as part of this group, will have the transaction language.
-
When adding Myself or an internal recipient:
-
If Override recipient language is enabled for the account, the recipient language will be set to Use Transaction Language.
-
If Override recipient language is disabled for the account:
-
If the recipient's preferred (sender) language is part of the supported languages, the recipient language will be set to their preferred language.
-
If the recipient's preferred (sender) language is not part the supported languages, the recipient language will be set to Use Transaction Language.
-
-
When replacing a placeholder recipient, the Use Transaction Language option will be selected by default.
-
When replacing a placeholder recipient, the "Use transaction language" option will be selected by default.
-
When replacing a placeholder recipient, the Use Transaction Language option will be selected by default.
-
When adding a recipient to a transaction or template from the sender interface:
-
For a Template or a Transaction that has never been sent, if the selected language is unsupported, the creation will fail with a message that reads The language defined for this template and/or one of the recipients is no longer supported by your administrator. Please select a different language.
-
For a Transaction that has been previously sent, if the selected language is different from the transaction language AND is not part of the list of supported languages, the creation will fail with a message that reads "The language defined for the recipient is no longer supported by your administrator. Please select a different language.
-
-
If the Transaction language is now unsupported, when adding or replacing a recipient and the Use Transaction Language is selected, the action will fail with an error that reads The language defined for the recipient is no longer supported by your administrator. Please select a different language.. The transaction language will need to be updated before you can add or replace the recipient.
Reassigning Recipients
By default this feature is OFF. If you toggle it ON, during the Signer Experience the recipient will be able to delegate their role in a transaction to another recipient. This action is available only for the Recipient and Group recipient types.
To reassign a recipient:
- Locate the transaction's Recipients section.
- Select the recipient, and click the ellipsis (...) in the last column.
-
Click Settings.
-
Select the Advanced tab.
-
Toggle ON the Change Signer option.
Changing a Recipient's Type
Once a recipient has been saved, their "type" can be changed.
You cannot change your own recipient type (Myself), nor can you change any other recipient to the Myself type.
To change a recipient's type in the Designer:
-
In the list of recipients, select the recipient whose Type you would like to change.
-
Select the drop-down menu next to their name.
-
Click Edit.
-
Select the Recipient tab, and modify the type as necessary.
To change a recipient's type in the transaction page:
- Locate the relevant transaction's Recipients section.
- Click the user's "recipient icon" (). A drop-down menu displays the type options:
- Select one of the recipient types in the following table.
Adding Reviewers
A Reviewer is someone who is given access to a transaction, so that they can review that transaction's contents. A Reviewer will be informed of the creation and the completion of a transaction, but is not otherwise involved. A transaction can have multiple reviewers.
To add a recipient as a Reviewer, simply add them to the transaction, but do not assign any signatures to them. A Reviewer can view information within the transaction (e.g., the transaction's current state; who has already signed; who has not yet signed).
Both individuals and groups can be configured as Reviewers.
Changing a Recipient's Personal Details
To change an existing recipient's personal details:
- Locate the transaction's Recipients section.
- Edit the recipient's details (e.g., First Name, Last Name, Email, Title, Company).
Typing the First Name, Last Name, or Email of an existing recipient invokes a list of matching users from: (1) the recipients’ history; (2) the list of account senders. For more on leveraging this functionality, see Adding Recipients to a Transaction.
Specifying the Signing Order
By default, the Set signing order toggle switch in the Recipients section is OFF.
To specify a Signing Order for a transaction's recipients:
- Locate the transaction's Recipients section.
- Toggle the Set signing order switch to ON. A number will appear beside each recipient in the list.
- Drag each recipient's drag handle (orange dots to the left of their recipient icon) up or down the Recipients list to their appropriate location. The number beside the recipient name will update based on the new signing order.
If the transaction is accessible to Screen Readers, a recipient can be moved to their desired location using the keys "up-arrow" and "down-arrow".
Configuring Other Recipient Settings
To change a recipient's settings:
- Locate the transaction's Recipients section.
- Select the recipient, and click the ellipsis (...) in the last column.
-
Click one of the following options:
Option | Settings | Notes |
---|---|---|
Edit details |
Allows you to edit specific recipient settings. The Type field displays the recipient's type, but is read-only. By contrast, you can change the following settings for the recipient: |
The Language field will be: (1) hidden for recipients of type Myself, Placeholder or Group; (2) disabled for recipients who are account senders (for them, the system will display the language assigned to their account). |
Add Authentication Method |
Selecting this opens the Authentication tab. This box enables you to specify the Authentication Method that will be used to verify the recipient's identity. This action is available only for the Recipient recipient type. |
For more information, see New. |
Edit signing method | Allows you to change the signing method for the selected recipient. For example, to force a recipient to use a Personal Certificate. | |
Add attachments request |
This box enables you to specify one or more supporting documents (e.g., a driver's license) that the recipient must upload before the transaction is completed. This action is not available for the Myself recipient type. Once the transaction is complete, the Transaction Owner can review, comment on, download, or reject the attachments uploaded by recipients. |
|
Advanced Settings | ||
Remove | Allows you to quickly remove a recipient from a transaction. |
-
After you've completed the above configurations, click Save.
Removing a Recipient from a Transaction
To remove a recipient from a transaction:
- Locate the transaction's Recipients section.
- Select the relevant recipient, and click the ellipsis (...) in the last column.
- Click Remove. You are prompted to confirm the action.
- Click Yes. A message confirms that the recipient has been removed.
This action is available for all recipient types.
Sending Transaction Reminders
After you have sent a transaction to its recipients, you can send them reminders that they have documents to sign.
To resend an invitation email to a recipient:
- Locate the transaction's Recipients section.
- Click the recipient's envelope icon. A message confirms that an email reminder has been sent.
To send another SMS code to a recipient:
- Locate the transaction's Recipients section.
- Click the recipient's mobile-phone icon. You're prompted to confirm the action.
- Click Yes. A message confirms that an SMS code has been sent.
This action is available only for recipients whose recipient type is Recipient, and whose Authentication Method is SMS Authentication.
Starting with the 11.42 release of OneSpan Sign, the Classic User Experience is no longer supported for SaaS customers. This section is thus only intended for on-premises customers who have not yet migrated to our Container deployment.
This section describes the following topics:
- Adding Signers
- Defining a Signer Workflow
- Adding a Signer Group
- Configuring Recipient Authentication
Adding Signers
Signers are added to a document package one at a time. By default, you are listed as a signer because you are the package owner. All signers for the current package are displayed in the Signers list.
To add signers to a package:
- From the Signers and Documents page, click Add Signer.
- Enter the Email, First Name, and Last Name of the signer.
- Optional: Enter the signer's Title and Company Name.
- Click Authentication to choose one of the following Authentication Methods: Email (default), Q&A, or SMS.
- Click Advanced to act on any of the following options:
- Personal Email Message Option
- Document Delivery Option
- Change Signer Option
- Click Save.
Adding Previously Added Signers
A signer that has already been added to a package can be added to another package using the following procedure.
To add a previously added signer to another package:
- In the Signers search box, type any consecutive alphanumeric characters of the name of the desired signer. A list of matching signers will appear.
- Select the desired signer.
Defining a Signer Workflow
By default, a package's signers can sign in any order. If a package contains multiple documents, each signer must sign the documents in the order in which they appear in the Documents list.
If it is important that signatures be obtained in a specific order, a Signer Workflow can be defined. When such a workflow is defined, signatures are obtained from signers in the order in which the signers appear in the Signers list.
For example, in the following screen: (1) Paul must sign first; (2) Joe will receive the package only after Paul has signed.
To define a Signer Workflow:
- From the Signers and Documents page, select the box Define a role workflow.
- To change the order of signers, drag the handlebar left of each signer's name to its desired position in the Signers list. The cursor will change to a crossbar.
Adding a Signer Group
To add an existing group in your account to a package:
- From the package's Designer page, click Add Signer. The Add Signer dialog box appears.
- For Signer Type, select This Signer will be: A Group defined in my account.
- Select the Signer Group you want to add.
- Click Save.