Bulk sign fields

SigningHub provides an efficient, fast, and easy way to sign multiple fields assigned to you, within a single document, in one go. For this, use the "Bulk signing" option to sign your fields through a single-click operation while the document is in a 'Draft' or 'Pending' state. Bulk signing duly works with document signing, reviewing, updating, in-person signing and adding your initials. However, SigningHub does not allow you to sign fields through bulk signing if:

Field-level (OTP or TOTP) authentication has been set to sign the field, or
The next configured recipient in a workflow is an undefined placeholder, or
The mandatory form fields assigned to you are empty
A mandatory attachment field has been assigned to you

The availability of the "Bulk Signing" feature is subject to your subscribed Service Plan and Enterprise Role. If you cannot find this option in your account, please ask your Enterprise Admin to upgrade your service plan and enable it in your Role>Document Settings.

Bulk sign fields within a document

Open a 'Pending' and 'Draft' document.
Click on the "Bulk Signing" button in the information panel, on the document viewer screen.
The bulk sign dialogue box will appear. It will list your documents based on the required actions.
Click on each of the following action buttons to bulk-sign the selected documents, based on your assigned recipient roles:
- Electronic Seals: Click on the 'Apply Electronic Seal' button, and the electronic seal will be applied.
- Basic Signatures: Click on the level of assurance, and the 'Sign' dialogue box will appear. Click the 'Sign' button to complete the signing.
- Advanced Signatures: Click on the level of assurance, select the signing server in the 'Sign' dialogue box, and then click 'Sign' to apply advanced signatures.

While a field is being processed, a circular percentage progress bar will appear next to it, to indicate the progress.
If a field can not be signed, the respective reason will be displayed, click on the 'Continue' button to continue signing the eligible documents.
If an initial field, then SigningHub will display a dialogue box to add your initials first.
If for any reason bulk signing fails, a summary dialogue will appear to show the reason for failure, and a caution icon will appear adjacent to the button.
If your textual signature is already filled in with your fixed name, it is because the signature text editing is restricted in your enterprise role. Your signature text can be edited under the "Signature" tab in 'Personal Configurations.
Choose a desired appearance for your signature. The options being populated in the "Signature Appearance Design" field are the allowed appearances to your enterprise user role. You can also see this list in your signature appearance. The signature appearance will be auto-filled and cannot be changed if it's restricted from enterprise roles signature settings to use a specific appearance for the selected Signing Server.
In case of bulk signing using a signature pad, the "Remember the captured signature for use throughout this document" option will not appear.
Upon clicking the "Sign" button, if any 'Authentication Method' is configured for the selected signing capacity under enterprise roles, an authentication dialogue box will appear. If no 'Authentication Method' is configured for the selected signing capacity under enterprise roles, the document signing process will start. In the documents, all the signature fields with the same level of assurance that matches the selected 'Signing Capacity', in the above step, will be signed.
If you have selected CSC Signing Server to perform signature and "Authorisation Code" is selected as the "Auth Type" in CSC Connector, then on clicking the 'Sign' button you will be shown an additional authorisation option, depending upon the authorisation settings configured in your CSC Server:
- Implicit
- Explicit (One Time Password (OTP)/PIN Number)
- OAuth Authorisation Code
All unregistered users using the CSC Signing Server to perform signatures will be shown an additional authorisation option, as mentioned above, upon clicking the 'Sign' button.
If "Client Credentials" is selected as the "Auth Type" in the CSC Connector and a valid CSC User ID has been configured for the user, then on clicking the 'Sign' button, no additional authorisation will be required for signing.
There could be a possibility that both the options of OTP and PIN number are configured as a signing time authentication by your CSC Server.
In case the Level of Assurance of a "Signature" field is set to "Simple Electronic Signature", then only Document Signing Authentication will work.
In case of signing of XML document, optionally you may also specify "Commitment Type Indication". SigningHub populates values of this field in editable mode from your Personal Signing Details. When specified they will become a permanent part of your XML signature.
In the case of OTP authentication, the OTP method will be 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
- "(SMS and Email)", in case both "Email OTP" and "SMS OTP" are configured in the service plan
If the user has authenticated once against an "Authentication Method" which is configured for a "Signing Capacity", the user will not be prompted to re-authenticate the same "Authentication Method" even if it is configured against a different "Signing Capacity". In case a different "Authentication Method" has been configured against the new "Signing Capacity", the user will be prompted to authenticate against it.

PreviousOTP authentication NextAdd drop-in comments

Last updated 5 days ago

Bulk sign fields within a document

Open a 'Pending' and 'Draft' document.

Click on the "Bulk Signing" button in the information panel, on the document viewer screen.

The bulk sign dialogue box will appear. It will list your documents based on the required actions.

Click on each of the following action buttons to bulk-sign the selected documents, based on your assigned recipient roles:

Electronic Seals: Click on the 'Apply Electronic Seal' button, and the electronic seal will be applied.
Basic Signatures: Click on the level of assurance, and the 'Sign' dialogue box will appear. Click the 'Sign' button to complete the signing.
Advanced Signatures: Click on the level of assurance, select the signing server in the 'Sign' dialogue box, and then click 'Sign' to apply advanced signatures.

While a field is being processed, a circular percentage progress bar will appear next to it, to indicate the progress.
If a field can not be signed, the respective reason will be displayed, click on the 'Continue' button to continue signing the eligible documents.
If an initial field, then SigningHub will display a dialogue box to add your initials first.
If for any reason bulk signing fails, a summary dialogue will appear to show the reason for failure, and a caution icon will appear adjacent to the button.
If your textual signature is already filled in with your fixed name, it is because the signature text editing is restricted in your enterprise role. Your signature text can be edited under the "Signature" tab in 'Personal Configurations.
Choose a desired appearance for your signature. The options being populated in the "Signature Appearance Design" field are the allowed appearances to your enterprise user role. You can also see this list in your signature appearance. The signature appearance will be auto-filled and cannot be changed if it's restricted from enterprise roles signature settings to use a specific appearance for the selected Signing Server.
In case of bulk signing using a signature pad, the "Remember the captured signature for use throughout this document" option will not appear.
Upon clicking the "Sign" button, if any 'Authentication Method' is configured for the selected signing capacity under enterprise roles, an authentication dialogue box will appear. If no 'Authentication Method' is configured for the selected signing capacity under enterprise roles, the document signing process will start. In the documents, all the signature fields with the same level of assurance that matches the selected 'Signing Capacity', in the above step, will be signed.
If you have selected CSC Signing Server to perform signature and "Authorisation Code" is selected as the "Auth Type" in CSC Connector, then on clicking the 'Sign' button you will be shown an additional authorisation option, depending upon the authorisation settings configured in your CSC Server:
- Implicit
- Explicit (One Time Password (OTP)/PIN Number)
- OAuth Authorisation Code
All unregistered users using the CSC Signing Server to perform signatures will be shown an additional authorisation option, as mentioned above, upon clicking the 'Sign' button.
If "Client Credentials" is selected as the "Auth Type" in the CSC Connector and a valid CSC User ID has been configured for the user, then on clicking the 'Sign' button, no additional authorisation will be required for signing.
There could be a possibility that both the options of OTP and PIN number are configured as a signing time authentication by your CSC Server.
In case the Level of Assurance of a "Signature" field is set to "Simple Electronic Signature", then only Document Signing Authentication will work.
In case of signing of XML document, optionally you may also specify "Commitment Type Indication". SigningHub populates values of this field in editable mode from your Personal Signing Details. When specified they will become a permanent part of your XML signature.
In the case of OTP authentication, the OTP method will be 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
- "(SMS and Email)", in case both "Email OTP" and "SMS OTP" are configured in the service plan
If the user has authenticated once against an "Authentication Method" which is configured for a "Signing Capacity", the user will not be prompted to re-authenticate the same "Authentication Method" even if it is configured against a different "Signing Capacity". In case a different "Authentication Method" has been configured against the new "Signing Capacity", the user will be prompted to authenticate against it.