Account-Level Features

Determines if Account Owners and Account Managers can edit their account’s settings. The editable settings include most of BackOffice's Account, Feature, Package and Signing settings that are Boolean and non-paid.

Default: true

Determines if a transaction's external signers can have the same email address. This possibility was developed to accommodate those rare cases in which relatives or spouses share the same email address.

Default: true

Note: (1) "External signers" are signers who do not have an email account attached to a Sender or other OneSpan Sign role. (2) 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.

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

Determines if a transaction's signers (external and internal) can have the same phone number. This possibility was developed to accommodate those rare cases in which people (e.g., spouses) share the same phone number.

Default: true

Note: This setting concerns the phone numbers used when SMS Authentication or ID Verification is configured for at least two signers.

Determines if the recipients of an In-Person transaction can host the transaction, provided they are also senders in the account. If this parameter is false, only the Transaction Owner can host the transaction.

If this feature is disabled, this list will be viewable only by the Transaction Owner.

Default: false

Determines if recipients will be able to upload attachments to a transaction. If so, senders can ask recipients to upload one or more attachments, and recipients can do so.

Default: true

Determines if senders can permit recipients to sign with a digital certificate that resides on a hardware token or Smart Card (e.g., CAC, PIV, eID).

Default: false

Determines if Custom Fields can be used.

A "Custom Field" is one that, at the time of signing, is automatically populated with data that is specific to the recipient.

Default: true

Determines if the Delegation feature will be available. This feature gives a user the ability to delegate access to their OneSpan Sign transactions to one or more other users on their account.

Default: false

Determines if no footer will appear in the application's User Interface.

Default: false

Note: This setting does not apply to the login page.

Determines if the Document Visibility feature will be available. This feature gives suitable users the ability to control which recipients can view specific documents in a transaction during the Signer Experience.

Default: false

By default, adding a recipient to a transaction will give that recipient visibility to all documents. As a best practice, we recommend that you set document visibility after all documents and recipients have been added to the transaction. If you need to add a recipient after you have set document visibility, be sure to verify the document visibility of the recipient you have just added.

Determines if the Signer Experience will be displayed to recipients whenever possible.

The Signer Experience currently has limited functionality. Thus it will be displayed to a recipient only if all the features enabled for the recipient's session are supported by the Signer Experience.

Default: false

Determines if the account’s senders will be able to see the account’s recipient history.

Default: true

Tip: Disable this feature if you want to prevent senders from selecting recipients from the account’s recipient history. This should minimize erroneous signer information.

External hyperlinks in document transactions can now be opened up by recipients who are signing those documents.

Determines if documents downloaded or sent via email to recipients will be flattened (read-only) before being sent.

If this feature is enabled, such documents will always be flattened. If this feature is disabled, documents will: (1) be flattened if the transaction has not been completed; (2) remain active if the transaction has been completed, so users can click to view signatures' properties.

This setting applies only to recipients.

Default: false

Determines if the Permanently Delete button in the sender part of the New User Experience is hidden. When that button is hidden, senders cannot permanently delete any transaction.

Default: false (button is not hidden)

Determines if users with sufficient permission can access system-created Transaction Reports and Account Reports from the New User Experience or API.

Default: false

Note: In-App Reports is not available in on-premises environments where OneSpan Sign was deployed using Docker containers.

Determines if the Mobile Signature type will be available when documents are being prepared for signing.

Default: false

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

Default: false

Determines if after selecting a recipient, Senders can add fields to a document without having added a Signature Block. Once a Signature Block is added, all previously added fields will be attached to it.

Default: false

Determines if signatures can be flagged as optional. When the Optional Signatures flag is set for a document, a recipient is not obliged to sign all of their signatures inside that document before completing the associated transaction.

Default: false

Determines if a sender’s Recipient Language specification for the recipient of a transaction will override any User Language preference that the recipient specifies in the Signer Experience.

Default: false

Note: BackOffice administrators can set this parameter either directly or via the Account Setting self-service. Senders can specify the Recipient Language either in the User Experience or via the API. Their specifications will override recipients' User Language specifications if this parameter is true.

Determines if senders can configure recipients to sign with the Personal Certificate Client when they sign with a certificate.

Default: false

Note: Even if this parameter is true, the associated feature won’t work unless the certificateSigning parameter is also true.

Determines if the system will impose on an account: (1) a maximum number of API calls in a given time (default = 20 calls per minute); (2) a maximum file size of documents in API calls in a given time (default = 100 MB per hour).

Default: true

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

Note: Rate Limiting does not apply to GET methods. It applies mainly to POST and PUT methods. It also applies to DELETE methods that perform an update operation (not a delete operation).

Determines if an account owner can manage the roles and permissions of the senders in their account. Note that roles are defined by their permissions.

When this feature is true, the system supports: (1) the default roles of Admin, Manager, and Sender; (2) the ability of account owners to create additional roles with customized permissions.

When this feature is false, the system supports the default roles of Owner, Manager, and Member.

Default: false

Note: Account Owners will be able to download the Evidence Summary for their senders if this Roles and Permissions feature is false for their account. If this feature is true for their account, such downloads will not be possible.

Determines if the unsigned required Signature Fields of a document in an incomplete transaction will be masked (i.e., blackened) when a flattened version of the document is downloaded.

Default: false

Determines if signers of the account’s transactions can apply their signature by uploading an image (e.g., the seal of a U.S. state).

Default: true

Determines if Senders can configure recipient authentication via a Digipass token.

Default: false

Determines if External Signer Verification will be available.

When this feature is enabled, a recipient trying to confirm their approval of a document within OneSpan Sign can verify their identity via their credentials with an external organization (e.g., DIGIPASS credentials).

Default: false

Determines if Transaction Owners will be required to log in to OneSpan Sign before they can access the Signer Experience.

Default: false

Determines if SMS Authentication will be available for signers who participate in the account’s in-person transactions.

Default: false

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

Default: true

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

Determines if a default value (ON or OFF) is configured for the Mask Response toggle switch that appears during Q&A Authentication.

Default: true

Determines if Single Sign-On Authentication (SSO) can be configured for external recipients.

If SSO is configured for external recipients, authentication information can be exchanged between OneSpan Sign and corporate servers, so recipients can use their organization's credentials to access the Signer Experience.

Default: false

This flag was introduced in OneSpan Sign 11.16, but the feature will become available only in a later release.

Determines if senders will be required to log in to OneSpan Sign via Single Sign-On Authentication (SSO).

Default: false

Determines if the Evidence Summary can be downloaded from the Signer Experience once all participants have completed the transaction.

Determines if the sender will receive an Evidence Summary document as an email attachment once a transaction is completed.

Default: false

Determines if a completed transaction's Evidence Summary will be signed and locked.

Default: false

Determines if the IPEN feature will be available — i.e., if documents can be electronically notarized during a face-to-face meeting between a Notary and signers.

When this feature is enabled, the Enable notarization setting is available when a transaction or template is created.

Default: true

Determines if the Remote Online Notarization feature will be available — i.e., if documents can be electronically notarized during a virtual meeting between a Notary and signers. This notarization process uses audio/video technology to connect a Notary and signers in different locations.

When this feature is enabled, the Remote Online Notarization setting is available when a transaction or template is created.

Default: false

Note: Even if this parameter is set to true, the associated feature won’t work unless the following parameters are also set to true: (1) Notary Management System; (2) Virtual Room; (3) Virtual Room Recording; (4) Personal Certificate Client.

Determines if signers can request and participate in ad-hoc co-browsing sessions.

Default: false

Note: Even if this parameter is set to true, the associated feature won’t work unless the Ad-hoc Cobrowsing Sender parameter is also set to true.