Bulksign supports 3 types of recipients :
These type of recipient are the actual signers of the documents.
For this type of recipient, one or multiple signatures will be applied automatically to the documents on behalf of the sender.
The role of the recipient is to approve and check the content of the envelope documents.
Receives Copy :
These recipients will receive a copy of the signed documents. Please note the "Receive Copy" can receive a document copy ONLY after all the signers have signed the document. If you add a "Receive Copy" recipient before the last signer of the envelope, it will be moved automatically after the last signer.
Besides the built-in access code security, as the sender of the document you have the possibility to add another layers of security :
Password : access to the document can also be protected with a password. Just please keep in mind that it becomes your responsibility to securely communicate the password to the recipient.
SMS code : (please note this is not available for license types) . When the recipient is trying to access the document, a OTP is generated and a SMS is sent to the recipient (to the phone number you, as a sender, you have set). The recipient has a few minutes to get the code and authenticate with it.
SAML/OAUTH : set up your SAML/OAUTH endpoint and the recipients will be authenticate by your organization usign that endpoint.
Manual Identity Verification : the recipient is required to take pictures of a ID card (passport, driver license or ID card). Based on these identity artefacts, the envelope sender decides to allow/deny access to the document.
To send a new document for signing, each signer must be assigned at least 1 signature field.
If the sender enables recipient delegation, a recipient can delegate singing to another person if he thinks he is not the right person to sign that specific document. The delegation can be done in 2 ways :
direct : if the recipient does not have authentication enabled, the delegation is done directly.
approved by sender. When the recipient has authentication, the sender has to approve the delegation and set new authentication options for the new recipient.