Creating a signature package with separate signers and a different sender still shows the sender's name in the list of signers in the signature box placement web GUIThursday, March 23, 2023 at 07:54pm
My goal is to enable an admin person to easily assist with a signature package (they will be the sender) but where the admin person is strictly the sender and will never be a signer.
I am exploring the following mechanism for creating signature packages using the OneSpan REST API. This is for documents for which we do not yet have templating set up, so we need the OneSpan web GUI signature box placement UI.
Using the REST API, we create a signature package with, say, two signers A and B and one sender C. We create the package in draft mode.
The sender C (the admin person) can then go directly to the signature package using the URL we know at this point (since we have the package id), log in, leave all signature package details as is (the signers, the authentication methods, etc.), click "Next", and then get to the signature box placement web GUI to place the signature boxes.
This all works fine in my tests.
The issue is that in the signature placement web GUI, there are three names on the left available to drop into the document to create signature boxes: signer A, signer B and sender C.
It seems strange and incorrect to present the sender's name as an option to use for creating signature boxes when they are explicitly set to be a sender only and not a signer.
I am wondering if there is any way to have only signer A and signer B's names shown in this scenario in the signature box placement web page.