eSign "on-behalf"

Hi Srini, Thanks for posting in our community! In OneSpan Sign, the out of the box function for this use case is called the "Groups"(guide here), with which, you can add the two signers to a single group and add the group as a role to the package. The limitation is that only senders can be added as group members, and you have sender limitation to your account. If you don't want to follow this path, you can consider to use the "optional signature" and fire a callback listener: (1)assign both signatures (for owner or a “power of attorney”) as optional and only contains optional signatures (1.5)you need to remove the default consent, because the "Accept" signature is mandatory for all signers other than package creator (2)once any one of the signer has signed, your callback listener will receive a "signer_complete" notification with package ID, so your application can programmatically mark complete (3)as long as the package has been completed, the other signer can only review the content. This workaround sounds not so straightforward, and requires all signatures to be optional, which works fine in a single signature scenario. Duo

Thanks Duo. I have some follow up questions: If we have multiple signers for the document and each of them can be also "on-behalf", then closing the package after one signer signed will not work. Also can we customize the eStamp for "on-behalf" scenarios? Currently we only get the "Esigned by John Doe on mm-dd-yyyy time".

Hi Srini, If the workaround doesn't work for you, you might have to consider the "Group" solution, here's some supplementary information regarding to the Group Signing: (1)I am informed by support team that if your account has the integration plan, there won't be sender number limitation (2)If you are in FedRAMP environment, because all group members have to be a sender, which means you will have to add all signers to your active directory. When signers clicked the "Go to Document" link from email notification, they will have to pass the 2FA first. (Allow to access sender SSO from email is a new feature introduced since 11.30) (3)If your signer clicked the link from email, after passing the 2FA, the page will lead them to the OneSpan Sign dashboard for the current implementation. If you want to lead them directly to the signing ceremony, you have to build the SP/IDP initiated SSO link and then send them by your application. We can have an Enhancement Request asking for redirecting to the signing page, if you are interested in this solution. For your second question, the signature eStamp format is an account level setting, per language. The default English template should looks similar to below:

  "signatureFormat" : "E-SIGNED by $signer_name;$line_break;on $date;"

Where the signer name and the signing date will be dynamically injected. Because it's not a package level setting, it'll be difficult to display different information other than name. And because the setting is per signer language, although it's not a good solution but you can consider using two different languages to mark the original signer and the delegated signer. Duo

Hi, I am following this up again. We do use the integration layer and API to do this and email are optional. But it would be nice have that enhancement for email please. Thanks. Srini.

For your second question, the signature eStamp format is an account level setting, per language. The default English template should looks similar to below: Can we request an enhancement to send in our custom "text for stamp" for the eSign which would override a default stamp? It looks like this would be a basic functionality for signing on-behalf?