Determines if a checkbox will appear at top of the page, enabling signers to accept the E-Consent document by selecting that box. This will save signers from having to scroll all the way to the bottom of the page to view the Accept button there.

Default: true

Determines if a transaction's signers (external and internal) can have the same first name and last name. This possibility was developed to accommodate those rare cases in which relatives or spouses share the same first and last names.

Default: false

Note: When both Allow Duplicate Signer Email Address and Allow Duplicate Signer Name are enabled, the Sender can choose to either merge the duplicate signers or keep them separate.

For Releases 11.47 to 11.51, this setting behaves as follows. If enabled, it allows a transaction's external signers to have: (1) the same full name AND the same email address simultaneously; (2) the same phone number.

As of Release 23.R3 (11,52), this setting is a master switch. If it’s enabled, the settings in the three previous rows are honored. If it’s disabled: (a) the settings in those rows are ignored; (b) this setting’s "legacy behavior" is restored. That legacy behavior, which characterized the system before Release 11.47, is this — a transaction's external signers can have: (1) the same full name OR the same email address, but not both simultaneously; (2) the same phone number.

Default: false

Note: "External signers" are signers who do not have an email account attached to a Sender or other OneSpan Sign role..

Caution: This feature does not work with Single Sign-On Authentication (SSO).

Determines if senders will be able to switch between the Classic User Experience and the New User Experience.

Default: false

Note: In the 11.35 release of OneSpan Sign, the part of the Classic User Experience designed for Senders became unavailable to SaaS users. This change does not yet affect on-premises environments where OneSpan Sign was deployed without Docker containers. If users in those environments want all of the Classic and New User Experiences to be available, they must set this feature to true.

Note: The Classic User Experience is not available in on-premises environments where OneSpan Sign was deployed using Docker containers. Users in those environments should therefore ensure that this feature is set to false.

Determines if the Bulk Sending feature will be available. This feature gives users the ability to create and distribute multiple transactions with minimum effort (by using a suitable template and a CVS file).

Default: false

Determines if senders can do the following within a single document: (1) apply various conditions (e.g., required, optional, enabled, disabled) to signature and input fields; (2) configure "conditional logic" (i.e., specify that a condition applied to one field will impose certain conditions on other fields).

Default: false

Default: true

Note: This feature is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.

Determines if signed documents can be delivered to signers as email attachments.

Default: true

Determines if the recipients in an In-Person transaction will not receive an email that invites them to sign.

Default: false

Determines if watermarks will be applied to documents that are downloaded by a recipient during the Signer Experience. The following watermarks are available:

• "OPTED_OUT" : "Void",
• "COMPLETED" : "Customer Copy",
• "DRAFT" : "Non-authoritative Copy",
• "EXPIRED" : "Void",
• "ARCHIVED" : "Void",
• "DECLINED" : "Void",
• "SENT" : "Non-authoritative Copy"

Default: false

Determines if the application's default User Interface will be the New User Experience.

Default: true

Note: In the 11.35 release of OneSpan Sign, the Sender part of the Classic User Experience became unavailable to SaaS users. This change does not yet affect on-premises environments where OneSpan Sign was deployed without Docker containers. If users in those environments want to use the Sender part of the New User Experience, they should set this feature to false.

Note: The Classic User Experience is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.

Determines if Signer Experience events will be recorded in e-Witness.

Default: true

Even if this setting is false, OneSpan Sign will record: (1) the screens from a Mobile Signer Experience; (2) the Guest Auth pages for SMS and Q&A Authentication Methods.

Note: e-Witness is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.

Determines if the Fast Track feature will be available. This feature permits the rapid distribution of transactions for signing, automates the e-signature process, and eliminates the need to send individual transactions to your recipients.

Default: true

Determines if an Account Owner or Manager will be able to manage Groups.

A "Group" is a collection of OneSpan Sign recipients who can act as a single recipient from the point of view of the transaction creator.

Default: true

Determines if Senders can add "imprint fields" to documents. An imprint field is a field that transaction recipients can see, but cannot interact with in any other way. Imprint fields are not associated with particular recipients.

Default: false

Determines if an account's Event Notifications interface will be displayed to the account owner in the User Interface. Event Notifications can then be used by third-party integrators to set up Event Notification callbacks from OneSpan Sign.

Default: true

Determines if the Mobile Signer Experience will be available to signers who access the Signer Experience from a mobile phone.

Default: true

Determines if during the Signer Experience the NEXT button always appears at the bottom of the page.

Default: false

Determines if countries can be blacklisted from accessing OneSpan Sign. If this feature is enabled, access will be blocked for any user (sender or signer) who tries to access the system from a blacklisted country.

Default: true

Determines if overlays will be applied when the system confirms a PDF's signed Signature Fields.

If this feature is enabled: (1) the system fetches the original (non-flattened) version of the PDF; (2) for the current signer and all previous signers, the system applies to each signed Signature Field an overlay that identifies: (i) who signed the field; (ii) when they signed it.

If this feature is disabled, the system simply fetches the flattened version of the PDF. It does not apply overlays.

The advantage of this feature is that when it’s enabled, it takes less time to load PDFs in the Signer Experience.

Default: false

Default: true

Determines if senders will be prevented from removing the Electronic Consent Document from a transaction or template.

Default: false

This feature’s action depends on whether Rate Limiting is enabled or disabled. If Rate Limiting is disabled, this feature is ignored. If Rate Limiting and this feature are both enabled, no limits are imposed on the account, but the system logs every time Rate Limiting’s limits are exceeded.

Default: true

Note: Imposing limits on an account requires both: (1) enabling Rate Limiting; (2) disabling Rate Limiting Report Only.

Determines if signers can send transactions to their mobile device for signing there.

Default: false

Determines if the system will stop a document's images from being rendered when the document is viewed in the Signer Experience.

Default: false

Determines if all recipients of a transaction must be assigned a Q&A, SMS, SSO, or KBA Authentication Method.

Default: false

Determines if recipients who are account senders will be required to log in to OneSpan Sign before they can access the Signer Experience.

Default: false

Determines if the account’s senders can ask recipients to authenticate themselves via our ID Verification method.

Default: false

Note: ID Verification is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.

Determines if an account's API Key will be displayed to the account owner in the User Interface. The API Key can then be used by third-party integrators to connect to OneSpan Sign's API.

Default: true

Determines if transaction recipients can be assigned KBA Authentication via LexisNexis.

Default: false

Determines if Q&A Authentication can be configured for recipients in the New User Experience.

Default: true

Determines if SMS Authentication can be configured for recipients in the New User Experience.

Default: true

Determines if signed documents and the Evidence Summary will be emailed to the sender as attachments upon a transaction’s completion. If this setting is true, both will be emailed.

Default: false

If this setting is false, and the evidenceSummary setting is true, only the Evidence Summary will be emailed. If both this setting and the evidenceSummary setting are false, no documents will be emailed.

Determines if the Evidence Summary for incomplete transactions can be downloaded from the part of the User Experience for senders.

Default: false

Determines if suitable users can access the Notary Management System. If so, those users can manage the notaries on their account (e.g., they can create a custom Role with notary privileges, and assign that role to users).

Default: false

Determines if senders can arrange ad-hoc co-browsing sessions for signers.

Default: false

Determines if account senders can create a virtual meeting room in which multiple signers from different locations can: (1) collaborate through a video conference call; (2) sign documents within a co-browsing session.

Default: false

Note: The Virtual Room is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.