SigningHub allows you to add signatures in a workflow. Read more about the types of signatures as per the level of assurance. Adding signatures for a recipient/ placeholder will consume signatures quota of your (document owner's) account, after being signed by the recipient. Once you add a signature field, the signature field is marked with "Signature". You can also add multiple signature fields for a recipient in a document. Adding a signature field is subject to your assigned enterprise user role. If you wish to use this provision, ask your Enterprise Admin to enable the respective signature field in your Role. Upon adding a signature field, a level of assurance will be set for a signature field which is set by default as per the configured default level of assurance under Signature Settings. Level of assurance options for a signature field is subject to your assigned enterprise user role, If you wish to use more options, ask your Enterprise Admin to enable the respective level of assurances in your Role.
Select the document from the information panel's 'Pages' tab, on which a signature is required from a signer. You can also manage the added documents from here.
Select the recipient from the information panel's 'Recipients' tab, for whom you want to add a signature field. You can also manage the added recipients from here.
Drop the "Signature" field on the required location on the document. By default, upon dropping the "Signature" field, the properties dialogue box is displayed.
Take the cursor to the signature field assigned to you in the document, and double-click the field. Alternatively, you could click on the field, and select the 'Sign' option. A signing dialog will appear to sign the field, only if this field is assigned to you and it is your turn to sign in the workflow.
Add your signature as required. Your signature field will be signed before sharing the document.
Click on the signature field in the document to delete, and select the "Remove" option.
The signature field will be removed from the document.
Click "Save". The field is placed. Once dropped, you can resize the field by changing its height and width using the bottom right corner to resize it diagonally as needed. The system will remember the field size and its display preferences (i.e., visible or invisible) for adding new signature fields of the same group accordingly i.e., all digital signature fields on the same documents package.
Enable this option to apply additional authentication at the field level when the recipient attempts to sign the document. This option is available in Draft, In-Progress, and Pending states. When enabled, the following authentication methods are available:
One-Time Password (SMS & Email)
This option will let the document owner send an OTP to the recipient that will used for the purpose of signing authentication. Whenever the recipient tries to sign this document, an OTP will be sent to the recipient's email, mobile number, or both, depending on the document owner's service plan configuration. When the service plan allows "SMS OTP", a field to specify the mobile number of a recipient to send an OTP will be displayed. The document will be signed only upon providing the correct OTP. By default, the specified number is displayed partially masked to comply with the GDPR policy. Click to view the complete number.
Do not show this dialog automatically when a signature field is added
Enable to automatically apply the "" of the current signature field to the ones that you will drop afterwards. This option is helpful when you need to drop several signature fields on the document without making an extra effort to manually set the same Level of Assurance for each of the signature fields separately.
Details Tab
Field Name
An auto-generated (unique) field name which is used when you need to sign this form field through the API calls. You can change the name as required, but make sure the uniqueness of a field name is not compromised i.e., two or more fields in a document cannot have the same field name. This field is only available when the status of a document is Draft.
Dimensions
Use this section to relatively set the on-screen and PDF coordinates/position (Left, Top, Width and Height) of the signature field. However, you can also manually move the field to the desired position in a document using drag and drop and these coordinates will be updated accordingly. These coordinates are only available when the status of a document is Draft.
Save and Cancel buttons
Click the "Save" button to save the configurations, or click the "Cancel" button to close this dialog.
Recipient
A read-only field to display the signer's name along with the email and/or the mobile number, based on the selected delivery method, for whom this signature field is being configured.
Level of Assurance
A mandatory field to be selected to perform signing for a user. Levels of assurance will be available as allowed in the role assigned to you. Level of assurance will be set for a signature field by default as per the configured default level of assurance under Personal Settings>Signature Settings. Level of assurance options for a signature field is subject to your assigned enterprise user role and can be changed under Role>Document Settings.
The terms for a level of assurance are as per the eIDAS Standards. For details of these terms click here. Possible values are:
Simple Electronic Signature (SES)
Electronic Seal (eSeal)
Advanced Electronic Seal (AdESeal)
Qualified Electronic Seal (QESeal)
Advanced Electronic Signature (AES)
High Trust Advanced (AATL)
Qualified Electronic Signature (QES)
In case the Document Owner tries to add a higher Level of Assurance in combination with Simple Electronic Signature (SES), then Simple Electronic Signature (SES) will be removed. For a smoother workflow, while adding more multiple signature fields on the document, the system will simply use the level(s) of assurance of the last field for the latest one instead of asking for every signature field. You can always modify the level of assurance for each field manually.
Visible
For a signature, this field will be available when you are allowed (in your user role) to add invisible signatures on a document. When available:
Enable the "Visible" option, if you require a visible signature from the signer in this field. This signature will have a proper appearance on the document as configured in the signer's Signature Appearance settings.
Disable the "Visible" option, if you require an invisible signature from the signer in this field. An invisible signature entails all the characteristics of a signature and is duly verifiable like a visible signature. However, it does not have any appearance on the document. When a signature field is marked as invisible, an eye icon is placed in the signature field (as shown with the red arrow):
​This Visible property is not available in case the Level of Assurance of the Signature field is set to "Electronic Signature".
In case you do not need to automatically display the properties dialogue box for the Signature fields that you will drop on the Viewer, then enable the "Do not show this dialogue box automatically when a signature field is dropped" option.
To prevent the bloating of a document with multiple Digital Signatures, if more than one Digital Signature fields are dropped against a single signer, only the last dropped signature field will be retained as a Digital Signature field, and the rest of the dropped signature fields will be converted to Simple Electronic Signature.
This conversion of Level of Assurance is individually applicable to each document with in a package i.e. each document can retain one digital signature field.
This conversion of Level of Assurance is applicable regardless of whether or not Simple Electronic Signature is allowed against a user's role settings, the system will still retain only the last dropped signature field as a Digital Signature field, and convert the rest of the dropped signature fields to Simple Electronic Signature, and the user will be able to sign it as well.
After the conversion of Level of Assurance:
if the user deletes the last added signature field, the system will update the Level of Assurance of the second-last added signature field to match the Level of Assurance of the deleted field.
if the user manually updates the Level of Assurance of a field which was converted to Simple Electronic Signature, the system will retain the updated Level of Assurance.
Let's understand this with an example: In this example, five Digital Signature fields have been dropped on multiple pages of a document, against a single signer. The last page (page 4) of the document has no signature for this signer. Only the last dropped signature field (fifth, on page 3) will be retained as a Digital Signature field, and the system will automatically convert the Level of Assurance of the rest of the dropped signature fields to Simple Electronic Signature (i.e. annotation).
In case the user has been assigned two signature fields:
the first one, a Digital Signature, and
the second one, a Simple Electronic Signature
At the time of signing, if the user tries to sign the digital signature field first, the system will generate an error as all the annotations including; Initials, In-person signatures, and Simple Electronic Signatures need to be filled in before moving onto a digital signature. (To complete the case: To sign the digital signature field, the user needs to sign the simple electronic signature field first.)
In the following cases, the "Authenticate signer" option is not available:
If the recipient is a group signer or a placeholder.
If the One-Time Password (OTP) and Time-based One-Time Password options are disabled in the service plan.
In the case of an Individual workflow type.
If there is an unprocessed signature/in-person signature field with the "Authenticate signer" option configured, the user will not be able to "Bulk Sign" and "Bulk Sign and Share" the document.
This OTP authentication option will only be displayed if the "Enable One Time Password (OTP)" option is enabled in the document owner's service plan. If you cannot find this option in your account, .
The OTP method for "Authenticate signer" will be the same as per the configured OTP method in the document owner's service plan.
"(Email)", in case only "Email OTP" is configured in the service plan
"(SMS)", in case only "SMS OTP" is configured in the service plan
In the "Mobile Number" field, enter the recipient's mobile number on which the OTP will be sent via SMS. The full international number must be entered in the 00 44 234334334 or +44 234334334 format. By default, the specified mobile number is displayed partially masked to comply with the GDPR policy. Click the 'Eye' icon to view the complete number.
If the signer's mobile number exists in the user's personal or enterprise contacts, the "Mobile Number" field will be auto-populated with the mobile number.
For the currently logged-in user, in case two different mobile numbers have been configured in the user's profile and the user's contacts, the system will auto-populate the "Mobile Number" field with the number configured in the user's profile.
When the delivery method is either "SMS" or "Email & SMS", the provided mobile number of the recipient will be auto-populated in the "Mobile Number" field.
The Time-based One-Time Password option will only be displayed if the "Enable Time-based One-Time Password (TOTP)" option is enabled in the document owner's service plan. If you cannot find this option in your account, .
If the user does not have two-factor authentication (2FA) configured, they will be prompted with a 'Configure Two Factor Authentication' dialogue to set up and provide a Time-based One-Time Password. If the user has already configured two-factor authentication (2FA) they will be prompted to provide the Time-based One-Time Password from the authenticator app configured on their mobile device.
To configure the two-factor authentication (2FA) the user will need to install an authenticator app (Google Authenticator, Microsoft Authenticator, etc.) on their mobile device. The 'Configure Two-Factor Authentication' dialogue shown to the user will contain:
QR Code
Manual Key
In case a recipient is changed and the "Authenticate signer" option is configured, the system will require the mobile number of the new recipient.
The following Authentication preference will be followed while signing, in case of configuration of field-level Authentication, Document Signing Authentication, and Secondary Authentication against the Signing Server:
You can only edit the on-screen dimensions, but not the PDF dimensions.
A signature field's level of assurance, once set as eSeal, QESeal, and AdESeal, is generated by using a certificate which is a public signing certificate as configured under the certification profile.
The availability of OTP security features is subject to your subscribed service plan. If you cannot find this option in your account, .
The OTP length is based on your subscribed service plan. SigningHub currently supports 4, 6, and 9-digit OTP.
An invisible signature doesn't have any visible appearance on a document. However, it entails all other verifiable characteristics of signing, i.e., Time Stamping, Certificate Chain, Certificate Status, etc.
You can also add a signature field on a previously signed document if the document is not certified or locked.
The document owner (and the shared folder collaborator, if any) can update the level of assurance of a "Signature" field while the status of the document is, "In-Progress" or "Pending".
In case the document owner is an enterprise user, they can set any level of assurance as allowed in the Enterprise Role.
In case the document owner is an individual user, they can set any level of assurance as allowed in the Service Plan.
Authenticate signer
To set up two-factor authentication (2FA), the user can either scan the QR code or manually enter the Manual Key into an authenticator app. After successful registration, the user must provide the Time-based One-Time Password (TOTP) generated by the app to proceed in SigningHub. A set of recovery codes is also provided in the configuration dialogue, which can be used in place of a TOTP to regain access if the user loses access to their mobile device. Each recovery code is valid for one-time use only, and it is strongly recommended to store them in a secure location. Users can regenerate a new set of recovery codes anytime from the Manage Two Factor Authentication (2FA). If an enterprise user loses access to both their mobile device and recovery codes, or has used all of them, they can contact their enterprise administrator to reset the two factor authentication (2FA) for their account.
No
-
Yes
Yes
Yes
Field-level Authentication
Yes
No
No
Field-level Authentication
Yes
Yes
No
Field-level Authentication
Yes
No
Yes
Field-level Authentication
No
Yes
No
Document Signing Authentication
No
Yes
Yes
Document Signing Authentication
No
No
Yes
Secondary Authentication against the Signing Server
The level of assurance of a signature field can not be updated if a read-only template has been applied.
Only the level of assurance of unprocessed fields can be updated.
Where previously, the level of assurance of a signature field was set to "Simple Electronic Signature (SES), the system will not allow updating the level of assurance.
Where previously, the level of assurance of a signature field was any other than "Simple Electronic Signature (SES), the system will not allow updating the level of assurance to "Simple Electronic Signature".
This authentication option will let the recipient sign the document after they have entered the Time-based One-Time Password. Whenever the recipient tries to sign this document, they will be prompted to enter the Time-based One-Time Password from the authenticator app configured on their mobile device. In case the recipient has not configured two-factor authentication (2FA), upon trying to sign a document that requires Time-based One Time Password, they will be prompted with a 'Configure Two Factor Authentication' dialogue to set up and provide a Time-based One-Time Password. The document will be signed only upon providing the correct Time-based One-Time Password.
Identity Verification
Requires the recipient to complete identity verification before signing the document. The verification is performed using the configured Identity Verification Profile at the enterprise level. If verification fails, signing is blocked. This option is only available if Identity Verification is enabled in the service plan and configured for the enterprise.
No
No
