Working with Ad Hoc Group Recipients

While adding a recipient to an Ad Hoc Group is generally a straightforward procedure, in certain scenarios the type of recipient being added affects the subsequent behavior of the transaction and signing process. This section will describe some of these situations.

Many of the scenarios described below are contingent upon the options that are enabled for your account. If you are not sure which options are enabled, contact our Support Team.

Working with Myself Type Recipients

It is possible to add the transaction owner (Myself recipient type) more than once to transactions containing Ad Hoc Groups.

When adding the transaction owner as an Ad Hoc Group member if they already exist as an individual signer (without a countersigner role) or as part of another Ad Hoc Group (or vice versa), the new signer will be added as a duplicate of the existing signer, linked to the same signer role. This applies whether the Countersigning feature is enabled or not on the account. The signing order will not be enforced in this case when Countersigning is enabled for the account.

The existing counter signing logic will remain as is when adding the transaction owner more than once as an individual signer to the transaction. That is, signing order will be enforced.

You cannot add the transaction owner as a member more than once to a given Ad Hoc Group.

When adding the transaction owner as a member to an Ad Hoc Group, if they already exist with one or more countersigners, the Ad Hoc Group member will be added with a new role OR will be linked to the first instance of the same recipient.

The table below outlines the different use cases and the expected behavior.

Working with Account Sender Recipients

It is possible to add the same account sender more than once to transactions containing Ad Hoc Groups.

When adding an account sender recipient as an Ad Hoc Group member if they already exist as an individual signer (without a countersigner role) or as part of another Ad Hoc Group (or vice versa), the new signer will be added as a duplicate of the existing signer, linked to the same signer role. This applies whether the Countersigning feature is enabled or not on the account. The signing order will not be enforced in this case when Countersigning is enabled for the account.

The existing counter signing logic will remain as is when adding the same account sender more than once as an individual signer to the transaction. That is, signing order will be enforced.

You cannot add the same account sender as a recipient more than once to a given Ad Hoc Group.

When adding an account sender as a member to an ad hoc group and that recipient already exists with one or more countersigners, the ad hoc group member will be added with a new role OR will be linked to the first instance of the same recipient.

The table below outlines the different use cases and the expected behavior.

Duplicate Recipients

OneSpan Sign allows for the use of Duplicate recipients. Duplicate recipients are signers who may, for example, have the same name and/or email address as another recipient.

When adding a duplicate recipient as part of a transaction a Duplicate recipients found dialog appears. This dialog allows you to confirm that you do want to use the same recipient to sign, and that you are not trying to create a different recipient, with the same credentials as the first.

• Link Recipient: Select this option to create a transaction using the same recipient.

• Add Recipient: Select this option if you are selecting a different recipient who may, for example, have the same name as another recipient and who has already been added to the transaction.

The behavior will change depending on the "Allow duplicate signers" configuration on the account.