“Invitee level options” provide various options to further modify the signing journey for the particular invitee.
By using “Invitee level options”, the sender of the document can set the retry attempts for Aadhaar signing, prioritize Aadhaar Esigning, restricting the signer from editing the name while signing, not showing the invitee's name in the signature, getting organizational or custom seal in the signature, and mandate the signer to upload the document while signing the document.
Note: This option has to be enabled for each invitee of the document
Once the document is created/workflow is created, on the invitee page click on “Invitee level options” which will lead to the side menu containing all the invitee level configurations.
Note: This option is only applicable for any Aadhaar Esign not any other types of Esigns.
Note: Retry attempts can not be set greater than 10.
Note: Signers can retry signing as many times as they like if no retry limit is set
Enabling the option “Don't allow invitee from editing name in signing journey” restricts the invitee (signer/reviewer) from editing their name while signing the document.
Note: This feature cannot be enabled for Automated Esign and NeSL.
Note: In case this option is disabled the signer will be allowed to edit their name while signing the document.
By default, the signer’s name configured during the invite or entered by him during the signing journey is placed inside the signature box.
Note: This feature cannot be enabled for Automated Esign and NeSL.
Enabling the option “Don't show invitee name in signature appearance” removes the invitee's name from the signature box.
Invitee Name has not appeared in this signature
Enabling the option ”Require company seal from invitee” while sending the document to get an organizational signature. Leegality will create a digital impression of a rubber seal and apply it on the signature of the signer.
Three types of company seals can be configured:
Note: Only one type of seal can be configured.
Once the document is signed, the company seal surrounds the electronic signature.
Note: If the option “Require company seal from invitee” is enabled but the organization name is not entered while sending the document, the signer can enter the company name and sign the document.
To read about the functionality of “Require invitee to upload supporting documents”, click here.
The option “Enable security features” provides additional authentications to make the signer identification more robust.
Enabling the option “Add custom URLs and webhooks” and enter the “Redirect URL” which will redirect the signer to the provided URL on completion/rejection of the transaction.
Enabling the option “Add custom URLs and webhooks” and enter the “webhook URL” (publically accessible URL to be used) which will provide the payload structure related to the document.
To know more about Webhook, click here.
Enabling the option “Add custom URLs and webhooks” and enter the “Error webhook URL” (publically accessible URL to be used) which will provide the payload structure related to the document in the three below cases:
If the Aadhaar Esign retry limit has been exhausted
If the Certificate details configured by the sender mismatch with the signer’s Certificate details.
If the invitation sent has Expired.
5. Webhook Version
There are four webhook versions that can be selected from the drop-down from the option “Webhook Version”.
Webhook 2.1 (This version is deprecated. Please use version 2.5)
Webhook 2.2 (This version is deprecated. Please use version 2.5)
Webhook 2.3 (This version is deprecated. Please use version 2.5)
Enabling the feature “ Set additional consent terms” will help in adding custom consent which will be added in the signing journey along with the default Leegality consent which can contain further Specific consent requirements to be agreed upon.
Note: Leegality default and custom consent both have to be agreed to proceed with the signing of the document.