SigningHub provides an efficient, fast and easy way to sign a pile of documents (up to 50) in one go. For this, use the "Bulk Sign" option to sign your (multiple) documents (in the "Pending" status) through a single click operation. Bulk signing duly works with document signing, reviewing, updating, in-person signing and adding your initials.

However, SigningHub does not allow you to sign those (pending) documents through bulk signing list, in which:

  • Permissions (password or OTP) have been set to open the document, or
  • Permission (Document Signing Authentication) have been set for the recipient, or
  • The set duration permission to open the document has expired, or
  • The next configured recipient in a workflow is an undefined placeholder, or 
  • The set delegate duration period has expired, or 
  • The mandatory form fields assigned to you are empty
  • Required Attachments recipient permission is configured


The availability of bulk signing option is subject to your subscribed service plan and user settings. If you are willing to use this provision, please ask your Enterprise Admin to enable it in your Role>Document Settings. 

Sign multiple documents in one go

  1. Click the "Documents" option, available at the top of the SigningHub screen.
  2. From your documents list, locate and select the pending document(s) to sign. You can select up to 50 documents.
  3. Click  from the appearing toolbar.

  1. The "Bulk Sign" dialog will appear, showing the list of selected "Pending" documents. Click  adjacent to any document name to preview it before signing. In case a legal notice is configured with any of the selected documents,   will appear against it under the "Legal notice" column header. Click it to review the legal notice details if required.
    In case a document could not be signed, the respective reason will be displayed under the "Status" column header. Such documents will be automatically un-selected. 

  2. Click the "I Agree to the legal notice(s)" check box to agree with all the configured legal notices with the selected documents. It is mandatory to agree with the legal notices before proceeding to sign.
    In case you have reservations on a legal notice clause, just unselect that document from the list to exclude it from the documents to sign batch. 

  3. Click the "Next" button to proceed to the documents signing. 



  1. After click on "Next" the the Signing servers dialog window will appear and display multiple signing servers which can be selected, based on the level of assurance set by the document owner on that signature field and the level of assurance that are configured in your role.
  2. Signing servers are based on service plan configurations, and will display the signing server for server-side and client-side signing both. 
  3. Select one of the signing servers to perform the signature. You can select from the options provided.




  1. In case any document has an initial field, then SigningHub will display a dialog to add your initials first.

See details how to add initials.

Click "Next" after adding the initials. The same initials will be added in all the selected documents with initials fields


  1. The "Sign" preferences will appear, specify a visible signature type, i.e. Draw, Text or Upload you wish to use in your signatures. 

If your textual signature is prefilled-in with your fixed name, it is probably because the signature text editing is restricted in your enterprise role. 
To edit your signature text: 

  • Use your Personal Settings> Hand Signature Method for Web Browsers> Text-based Signatures, if you are using a web browser for signing. Or  
  • Use your Personal Settings> Hand Signature Method for Mobile Apps> Text-based Signatures, if you are using a mobile app for signing.
  • Select a desired Signing Capacity for your signature (if it is configured for you to sign in different positions in your organisation). The options available in the "Signing Capacity" drop-down list are those that are allowed in your enterprise user role. All signing capacities will group together based on level of assurance.
  • 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 personal Signature Appearance.Signature appearance will be auto filled and cannot be changed if it's restricted from enterprise roles signature settings to use specific appearance for the selected Signing Server.
  • Click on the SIGN NOW button to proceed with signing.

 

  1. Upon clicking the SIGN NOW button, either no dialog window appears (if No Authentication is set for the selected signing capacity), or a dialog window appears depending upon the authentications that are configured for the selected signing capacity under enterprise roles>signing servers>authentications.
  • If you have selected CSC Signing Server to perform signature, then on click SIGN NOW button it will show you one of the options additionally, depending upon authorisation settings  configured at your CSC Server:
  1. Implicit 
  2. Explicit (One Time Password (OTP)/PIN Number)
  3. OAuth Authorisation Code

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. 


  1. The signing process will start.
           In case a document could not be signed, the respective reason will be displayed under the "Status" column header. Such documents will be automatically un-selected. 
  2. The selected documents will be signed right away and the signing status will be displayed accordingly. Click the "Done" button to go back to documents listing screen.


      
  1. Based on your signing details, the bulk signing feature supports both the server side signing and client side signing methods.
  2. SigningHub supports the "Bulk Signing" operation through Remote Authorised Signing (RAS) as well. This can be done by sending a single authorisation request from your mobile device running a SigningHub mobile app. For more details about what is Remote Authorised Signing, see the FAQs on Partner Portal.
  3. Font color will not be applicable in Signature Appearance while perform signature on any PDF/A document with "CMYK" color space ​​in order to ensure PDF/A compliance.
  4. Bulk signing duly supports signing Word files and XML files.
  5. SigningHub produces the "XAdES-Baseline-LTA" ETSI compliant signatures for XML document but for backward compatibility with ADSS Server version 6.9 or lesser SigningHub will produce the XAdES Extended signature on base of key "ES-X-L" added in web.config file.
  6. You must agree to all the legal notices configured with the selected documents before signing them.
  7. The system will prompt for OTP or password before showing the document preview, if it is enabled for any of the selected documents.
  8. You can sign up to 50 documents in one go through bulk signing. Contact sales if you are looking to extend this limit.
  9. Whenever a pending document is digitally signed, the digital signatures quota of the respective document owner's account is consumed, and hence their available count is decreased by one. 
  10. The availability of "Bulk Sign" 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.
  11. In case the Level of Assurance of a "Signature" field is set to "Electronic Signature", then Signing Servers will not appear on the signing dialog.
  12. SigningHub supports the "Bulk Signing" operation with the selected signing capacity for a particular level of assurance similar to the one configured by document owner for the signature field.
  13. You cannot perform "Bulk Signing" without adding attachment if Required Attachments recipient permission is configured under "Allow Attachments and Merging".


See Also