When you receive a document for signing/reviewing/editing/hosting in-person signatures, it is shown with the "Pending" status. You are also notified through an email from SigningHub with the link of the shared document. Since each pending document is associated with a workflow, they are shared with certain exclusive permissions (e.g., printing, downloading, access duration, password protection, etc.) by the respective Document Owner.

Sign a pending document

1. Click the "Documents" option in the navigation panel.

2. From your documents list, locate the pending document to sign, and click the "Sign" button in the information panel. The for signing. (Alternatively, you can skip the above two steps and follow the document link in the notification email that has been sent to you by SigningHub. This will directly for signing.)

3. as required (optional).

4. as required (optional).

5. Use the allowed as required (optional).

6. Fill in the (if any are configured for you).

7. Fill in the (if any are configured for you).

8. Add your (if any are configured for you).

9. Add your (if any are configured for you).

10. Add your (if any are configured for you).

11. Agree to the (if any is added).

12. Add (if necessary).

13. As per configuration, add your , and click the "Close" button.

14. Add (if any).

15. (if any).

In case you don't agree with the document's content or with any of its clauses, you may refuse signing and decline the document.

When you receive a document with merging permissions, you can merge other documents with it before signing. The merged documents by you will be fused with the actual document and are automatically signed along with the document signing.

Append a document

1. Click on the 'Append' option button appearing in the document viewer header. Alternatively, navigate to the "Pages" tab in the information panel, and click on the 'Append' button.

2. From the drop-down, select if you'd like to append at the top or bottom.

3. From the 'Add a document' dialogue box, add the document that you want to append.

4. Choose "Append at the top" or "Append at the bottom".

5. Click the 'Add' button. The PDF will be merged with the selected document and displayed accordingly.

Opening a pending document is subject to the , as configured for you by the respective . When you try to open a pending document to process:

• Either by clicking the "Sign" button, or

• By following the document link from your notification email, you could face any/ all/ none of the following viewing restrictions:

When you receive a document with some attachments, you can view and download them as required. You can also fully manage (i.e. add and remove) before signing if it has been permitted to you by the document owner. The attachments added by you will also be available to the next recipients in the workflow, along with other attachments (from the document owner). All these attachments become part of the document hash in the workflow.

Downloading attachments is subject to the following configuration:

• The "Allow Download" recipient permission is set against the workflow.

The Artificial Intelligence (AI) tab in the document viewer allows users to apply AI-powered actions to documents to streamline workflows, analyse content, and detect potential issues. Users can simplify content, summarise text, analyse legal implications, and detect inconsistencies or errors within a document.

The AI tab appears as the third tab in the Document Viewer and is available only when the Artificial Intelligence (AI) option is enabled for the user in Recipient Permissions.

Apply AI to the document

Stamp fields are filled by the assigned recipients during the signing workflow. Only the recipients assigned to a particular stamp field can fill it, ensuring proper workflow compliance. Multiple stamps can be filled by a recipient if more than one stamp field is assigned.

Access to enterprise and personal stamps is controlled by your role and the permissions assigned by your Enterprise Admin. Only allowed enterprise stamps, and your personal stamps will appear in the Your Stamps dialogue.

Apply a Stamp

Bulk document signing via server-side processing enables multiple documents to be signed in a single operation, significantly reducing processing time for enterprises dealing with large document volumes. This feature is particularly useful for industries like finance, legal, and corporate contract management, where a standardized signing approach is required. By ensuring uniform signing policies across all documents in a batch, organizations can streamline operations while maintaining compliance. Supported signing methods for server-side bulk document signing including ADSS, RAS, and CSC signing.

Signing Behavior w.r.t Signature Appearance

The section details the signing behavior of the system with respect to whether the signature appearance and the logo have been configured against a signing server. Breakdown has been given on the basis of the two subscription types; Enterprise subscription, and Individual subscription.

• Enterprise Subscription

• Individual Subscription

Server-side signing allows documents to be signed automatically on the server without requiring end-user interaction. This method is ideal for automated workflows where signatures are applied based on predefined rules, ensuring efficiency and compliance. Organizations handling large-scale batch signing, automated contract approvals, or enterprise-level document workflows can greatly benefit from this approach. SigningHub supports various signing methods under server-side signing, including ADSS signing, RAS signing, CSC signing, and eID Easy signing for both single and bulk document processing.

Single document signing through server-side processing enables an individual document to be signed automatically via API using server-side certificates. Since the signing process occurs without user intervention, it provides an efficient and secure way for businesses to handle legally binding signatures programmatically. This method enhances security by utilizing server-stored certificates and ensures compliance with digital signature regulations, making it particularly useful for industries requiring automated, high-trust signing solutions. SigningHub supports ADSS, RAS, CSC, and eID Easy signing for single documents.

With single document signing on the client side, users can sign an individual document using their locally stored signing credentials. The process requires user authentication and approval, ensuring a high level of security and legal compliance. Since the private key remains under the user’s control, this method is commonly used for high-trust digital signatures in regulated industries. The ability to manage signing credentials locally provides greater flexibility while maintaining compliance with digital signature standards. SigningHub supports T1C signing and Go>Sign signing for this method.

A legal notice is used to define certain terms and conditions that must be agreed by the signer, before signing. When you receive a document with a legal notice, you will be prompted to agree with it at the time of signing.

Agree to the legal notice

1. .

2. Click "Go to field" or scroll directly to your assigned signature field.

3. Double-click the signature field, or single-click and choose the "Sign" option.

4. The associated legal notice will be displayed in a dialogue box with the "I Agree" and "Cancel" options.

5. Click "Agree".

SigningHub lets the document owner, and the recipients add document comments with in the workflows. The document owner and the recipients can add document comments to a workflow for which the document owner has . Document comments can be added in all modes. i.e. Draft, Pending, In-progress, Signed, Declined, Approved, Submitted, and Completed. Once a document comment is added, depending on whether it is a public comment or a private comment, the users will be notified (via push notifications/on-screen notifications/email notifications) as per their and . In case the user is a document owner, the "When my documents are processed by others" notification setting will be followed. In case the user is a recipient, the "When there are subsequent changes in documents that I received" notification setting will be followed.

Add a comment

When you receive a PDF form document with any , the "Save" option will be listed under the three-dot menu of the document viewer header. The PDF form fields can be related to any information and these fields are displayed in yellow-orange color. Once saved, such information will become the permanent part of the signed PDF document.

Fill in the form fields of a PDF form

When you receive a document with any form components or form fields that have been assigned to you, the "Save" option will be listed under the three-dot menu of the document viewer header. The , are particularly related to your Name, Email, Job title, Company, Date, etc. and these fields are displayed in yellow-orange colour. SigningHub will pick the required information (where applicable) from your system profile and will display it in the respective fields in editable mode. You can change any field value (data) as required. Once saved, such information will become the permanent part of the signed PDF document. Moreover, SigningHub embeds fonts, graphics, annotations, and other necessary content within a PDF file to make your documents fully compliant with the PDF/A-1b standard. This content embedding is required by ISO 19005-1 and is usually associated with a document's visual appearance. However, a processed PDF through SigningHub may show non-compliance with the PDF/A-1b standard when a Date field or transparent PNG image rendering is used in it.

Fill in a form component field

Filling in is almost the same as signing a document, however digital signatures are not embedded in this case. They can be added through freehand drawing, text filling or image upload (the same way a signature is added). When you receive a document with , then you need to fill in all such fields before signing. This is to ensure that you have gone through all the important sections/ pages of the document, where initials fields were configured. Once you are done with your initials, you can sign the document.

Add your initials

SigningHub provides a robust set of APIs that allow seamless integration of electronic signature workflows into applications. The Signing Flow via API enables developers to manage signing operations programmatically, offering flexibility for both server-side and client-side signing approaches.

By using these APIs, organizations can automate document signing workflows, enhance security, and ensure compliance with regulatory standards. The Signing Flow via API is divided into:

• Server-side signing: Signatures are applied without requiring user intervention.

SigningHub provides the Delegated Signing facility through which you can assign your signing authority to a trusted person to collaborate in a workflow on your behalf. When you receive a document with the "" permissions, you can replace yourself with another recipient in the workflow. The delegated contact can then process the document on your behalf by using their own private key. The signature field will show the delegated signer name, however, the signature verification dialog will show your name (the actual signer's) along with a "Delegated" caption. If you are a part of any enterprise, and looking to replace yourself (i.e. Delegate other user) or change other configured recipients/ placeholders with a guest user, then you must have the option un-selected in your assigned role.

Delegate your signing authority

Client-side signing enables users to sign documents using locally stored credentials or hardware tokens, ensuring that they have direct control over their digital signatures. Unlike server-side signing, this method requires user interaction and is commonly used for high-assurance signatures, such as qualified electronic signatures. Client-side signing is particularly beneficial when users store their certificates on USB tokens or smart cards, allowing for enhanced security through user authentication before signing. SigningHub supports T1C signing and Go>Sign signing for both single and bulk document workflows.

Bulk document signing on the client side allows users to sign multiple documents in one operation while using their local signing credentials. This method is highly efficient for professionals and organizations that regularly process contracts, agreements, or compliance documents. By reducing manual effort in repetitive signing tasks, client-side bulk signing saves time while ensuring that signing keys remain under user control. This approach is particularly useful for organizations requiring high-assurance digital signatures while maintaining compliance with industry regulations. SigningHub supports T1C signing and Go>Sign signing for client-side bulk document signing.

When you receive a document with printing, downloading and adding text permissions, you will see these options available for the document. The text-adding provision lets you add any textual notes to the document before signing. When specified, the added text will become the permanent part of the signed PDF document.

Print a document

1. Click the "Documents" option in the navigation panel.

2. Select the document and click the "Print" button in the information panel.

3. A provision will appear through which you can set your preferences to print the document.

Download a document

1. Click the "Documents" option in the navigation panel.

2. Select the document and click the "Download" button in the information panel.

Add text to a document

1. .

2. Click the "Add Text" option listed under the "Fields" section and drop it on the document. In case the "Add Text" option is not listed, you cannot add text to this document because of adding text restrictions.

3. A blank text field will be added to the document. Drag and drop the text field anywhere in the document by using your mouse.

SigningHub allows you to change the workflow recipients even after sharing the document, provided it is allowed in your role. You can change all those recipients who have not collaborated (signed/ reviewed/ updated/ hosted the in-person signatures) in the workflow yet. Similarly, you can also update the placeholder fields with the actual recipients. When a configured recipient is changed/ replaced with another recipient, all the special privileges configured for the previous recipient will be transferred to the new recipient, along with the predefined workflow role (i.e. signer, reviewer, editor, or meeting host).

Change a recipient

1. Click the "Documents" option, in the navigation panel.

2. Open an 'In-progress' document, whose recipient you want to change.

3. Click the 'Details' button in the 'Recipients' tab in the information panel.

4. The recipients will be shown in an editable mode in the information panel.

5. Specify the Name, National ID or Mobile Number of the other recipient that is added to your SigningHub contacts list as required, and the email will automatically be updated in the below field.

Update a placeholder

1. Click the "Documents" option, in the navigation panel.

2. Open an 'In-progress' document, whose recipient you want to change.

3. Click the 'Details' button in the 'Recipients' tab in the information panel.

The newly configured recipient will be notified through an email upon their turn in the workflow.

When you receive a document with some attachment fields assigned to you, you can add attachments, as required. After adding an attachment and sharing the document, the attachment field does not become part of the document. When you receive a document with attachment fields assigned to you, then you need to add attachments to these fields, as required by the document owner, before signing. This is to ensure that you have provided all the required attachments that are requested by the document owner. If the attachment field is compulsory, you will only be able to sign the document after you have added an attachment to the attachment field.

Downloading attachments is now bound with downloading a document, which is subject to the following two configurations:

• The 'Allow document downloading' recipient permission is set against the workflow.

• The "Allow workflow participants to download document only on workflow completion" in the document owner's .

Add your attachment

1. Click the "Go to field" button or scroll to the field.

2. Single-click and then click the "Upload" option.

3. A dialogue will appear. Select the document you want to attach.

Preview your attachment

1. Take the cursor to the attachment field for which an attachment has been added.

2. Click on the field, and select the 'Preview' option.

3. A dialogue box will appear to preview the attachment.

To perform RAS signatures via API using server-side signing, follow the steps mentioned below. These steps outline the necessary API calls and conditions to successfully complete a single document signing operation through the server.

1. The signatory is identified via the access token provided in the API call, which means authentication is required before initiating the signing process. The access token must be issued directly to the signatory through authentication API.

2. If modifications are needed before signing, the Fill Form Fields API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.

3. To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the API. This API provides details of all available signing servers along with their corresponding levels of assurance.

4. Signature applications can use API to sign a single document. This API will respond with a "Pending" status if all validations are done. At this point, the server will send the authorization request to the client device.

5. API will be used to get the status of signing that were processed by the previous API call (repetitive call until status become COMPLETED).

   1. You will get verification object in the response of this API if the request parameter skip_verification is not passed or set to false. (on success)

6. After the signing process is complete, if the signatory is the final signer, the API must be invoked. Without this step, the document will remain in an "In Progress" state for the owner. Once the API is called, the status updates to "Completed."

7. Finally, after signing, the API can be used to retrieve the verification response.

SigningHub allows you to post comments (up to 255 characters) in a document workflow to accommodate any extra communication between the stakeholders (i.e. document owner & configured recipients). This may include the approval and declining reasons. The posted comments are maintained separately in the workflow, and will not be part of a completed/ signed PDF document. You can post your comments even after signing the document. Adding comments is subject to your assigned enterprise user role. If you are willing to use this provision, ask your Enterprise Admin to enable it in your Role>Document Settings.

Add a drop-in comment

1. Click on the document comments button to drag and drop the drop-in comment field anywhere on the document. Once a drop-in comment field is dropped, the field will no longer be draggable. The document field is not resizable.

2. Once the document comment field is dropped, the comment dialogue box will open.

3. Users can configure if they want to post a public comment or a private comment. By default, "Everyone" is selected for posting a public comment. For a private comment, the user can choose the recipient(s) who can see this comment. Only public document comments will be visible to all the recipients. The private document comment thread will only be visible to the selected recipients.

4. In the comment field, specify the comment you want to post. You can also choose to mention a recipient by typing "@". The maximum length of the comment is 500 characters.

5. Click on the "Add comment" button and the document comment will be posted.

Reply to a drop-in comment

The user can reply to a document comment to start a thread.

1. Click on the drop-in comment to which you want to reply.

2. A dialogue will appear. Type your reply and click "Reply".

Users can scan the QR code from a printed document, the scanner will generate a URL e.g. https://beta.web.signinghub.com/document/27a8095c-6fc4-4888-9b8a-b0a52f2c7eaa which will display a screen with document name and two options "View Document", "Verify Signature".

Screen Details

To perform RAS bulk document signing via API using server-side signing, follow the steps mentioned below. These steps detail the API calls required to sign multiple documents in a single operation through the server.

1. The signatory is identified via the access token provided in the API call, which means authentication is required before initiating the signing process. The access token must be issued directly to the signatory through authentication API.

2. If modifications are needed before signing, the Fill Form Fields API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.

3. To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the API. This API provides details of all available signing servers along with their corresponding levels of assurance.

4. The signature application needs to call API. This API executes pre-signing validations for each document package and respectively returns any errors along with the list of tasks that the application needs to perform to complete the signing process.

5. The signature application needs to call API. This API will sign/sign & share and share multiple documents without displaying the documents to the end user. This API will respond with a "Pending" status. At this point, the server will send the authorization request to the client device.

6. API will be used to get the status of a specific bulk signing transaction along with the details of document packages that were processed by the previous API call (repetitive call until status becomes COMPLETED).

7. Finally, after signing, the API can be used to retrieve the verification response.

Hosting in-person signatures on a document is also a part of the document workflow and is used for approval purposes. However, the hosting activity does not involve digital signatures. Being a you need to facilitate the document signing process for the configured in-person signers. Since hosting in-person signatures is a workflow activity, these documents are shared with certain exclusive permissions (e.g., printing, downloading, access duration, password protection, etc.) by the respective .

Host in-person signatures

SigningHub lets you view the verification details of each digital/e-signature/in-person signature performed on your PDF document. The verification details reveal the validity of the signature and display its associated information i.e., reason, location, contact information, local time at which signing was done etc.

View the verification details of a signature

To perform Go>Sign signatures via API using client-side signing, follow the steps mentioned below. These steps guide you through the required API calls and user interactions needed to complete the single document signing process on the client side.

1. The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.

2. If modifications are needed before signing, the

To perform Go>Sign bulk document signing via API using client-side signing, follow the steps mentioned below. These steps outline the APIs and user actions involved in signing multiple documents directly from the client side.

1. The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.

2. If modifications are needed before signing, the

To perform T1C bulk document signing via API using client-side signing, follow the steps mentioned below. These steps outline the APIs and user actions involved in signing multiple documents directly from the client side.

1. The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.

2. If modifications are needed before signing, the

To perform ADSS signatures via API using server-side signing, follow the steps mentioned below. These steps outline the necessary API calls and conditions to successfully complete a single document signing operation through the server.

1. The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.

2. If modifications are needed before signing, the

To perform T1C signatures via API using client-side signing, follow the steps mentioned below. These steps guide you through the required API calls and user interactions needed to complete the single document signing process on the client side.

1. The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.

2. If modifications are needed before signing, the

If for any reason, you do not want to sign/review/ update/ host a document that is sent to you for the respective purpose, SigningHub gives you an option to decline it.

Decline a pending document

1. .

Introduction

SigningHub allows its users to sign Word documents (having the .docx format) containing a signature line. The documents are allowed to retain their original format and are not converted to .pdf. This requires the configuration of a signing profile and a verification profile in ADSS. Configuration of a connector, a signing profile, a verification profile, and a service plan in SigningHub Admin. Once the configurations have been made, create a workflow with a Word document, and share the workflow. After sharing the workflow, sign the document via either SigningHub API or SigningHub Web.

XAdES-X-L (XAdES-X with Long-term Validation Data)

XAdES-X-L, short for "XAdES-X with Long-term Validation Data," is an advanced electronic signature format supported by SigningHub. This signature format aligns with ETSI standards, specifically tailored to meet European requirements for qualified electronic signatures. XAdES-X-L extends the capabilities of XAdES-X signatures by incorporating Long-term Validation Data. This ensures the long-term integrity and availability of validation data associated with the signature.

How it works?

1. Configure a signing profile as a prerequisite, in ADSS.

2. Configure a verification profile, in ADSS.

3. Configure a connector, in SigningHub Admin.

Configure a Singing Profile in ADSS

For Word document signing a signing profile is configured in ADSS Signing Service.

To configure a signing profile for signing a Word document, follow these steps:

1. In the "Select Signature Type" section, check "PKCS#1" and copy the Profile ID because it would be used in SigningHub Admin. Then click the "Next" button.
2. In the "Advanced Settings" tab, enable the "Hash Signing Settings", and click the "Save" button.

Configure a Verification Profile in ADSS

For signature verification, a verification profile is configured in ADSS Verification Service.

To configure a verification profile, follow these steps:

1. Copy the Profile ID because it would be used in SigningHub Admin.
2. SigningHub creates the PKCS#1 signature for using the signing service. In the "Signature Settings" tab, make the following changes:

Configure a Connector in SigningHub Admin

Make the following configurations to a connector in SigningHub Admin:

1. In the "Basic Information" section, choose "ADSS Server" as the "Provider".
2. In the "Details" section, fill in the required fields.

Configure a Signing Profile in SigningHub Admin

Make the following configurations to a signing profile in SigningHub Admin:

1. Paste the earlier copied Profile ID, while creating a Signing Profile in the ADSS:

Configure a Verification Profile in SigningHub Admin

Make the following configurations to a verification profile in SigningHub Admin:

1. Paste the earlier copied Profile ID, while creating a Verification Profile in the ADSS, in the highlighted field below

Add Signing Profile and Verification Profile to a Service Plan

Make the following configurations to a service plan in SigningHub Admin:

1. Select and add the earlier configured Signing Profile and Verification Profile, in a service plan in SigningHub Admin, as shown below:

SigningHub API Configurations

Make the following configurations to the SigningHub API:

1. Get the authentication token of a user using the SigningHub API.

2. Add a document package from the SigningHub API.

3. Upload the document via stream/base with the document extension .docx. Set the "x-convert-document" to false.

Signing via SigningHub API

To sign the document via the SigningHub API:

1. Sign the workflow.

2. In case of bulk signing, use the below API.

Signing via SigningHub Web

To sign the document via SigningHub Web, follow the steps:

1. Open the SigningHub Web and open the Word document through the document listing. Click on the signature field and then click "Sign".
2. After signing the document, you can view "Signature Verification" for details.

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

1. Open a 'Pending' and 'Draft' document.

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

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

Reviewing is also a part of document workflow and is used for approval purposes. However, the reviewing activity does not involve digital signatures. Being a reviewer you can either approve the document or can simply decline it. Since reviewing is a workflow activity, these documents are shared with certain exclusive permissions (e.g. printing, downloading, access duration, password protection, etc.) by the respective Document Owner.

Review a pending document

1. Click the "Documents" option, available in the left menu of the SigningHub screen.

2. From your documents list, locate the pending document to review, and click the "Sign" button against it. The for review. Alternatively, you can skip the above two steps and follow the document link in the notification email that has been sent to you by SigningHub. This will directly for review.

3. as required (optional).

4. as required (optional).

5. Use the allowed as required (optional).

6. Fill in the (if any are configured for you).

7. Fill in the (if any are configured for you).

8. Add your (if any are configured for you).

9. Add (if any).

10. Click the "Approve" button from the right of the document viewer header, and agree to the (if any configured for you).

11. Specify your reviewing comments (up to 500 characters), and click the "Approve" button. These comments will be available to:

    1. The respective document owner in the and .

    2. All the recipients in the comments section, and also in the notification emails of those who have configured emails for subsequent changes in the document.

The document is now approved, and its status will be changed from "Pending" to "Approved" in your documents list. The document owner will also be notified about this action through an email.

To perform ADSS bulk document signing via API using server-side signing, follow the steps mentioned below. These steps detail the API calls required to sign multiple documents in a single operation through the server.

1. The signatory is identified via the access token provided in the API call, which means authentication is required before initiating the signing process. The access token must be issued directly to the signatory through authentication API.

2. If modifications are needed before signing, the Fill Form Fields API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.

3. To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the API. This API provides details of all available signing servers along with their corresponding levels of assurance.

4. The signature application needs to call API. This API executes pre-signing validations for each document package and respectively returns any errors along with the list of tasks that the application needs to perform to complete the signing process.

5. If OTP authentication is turned on for the server-side signing operation which could be found in the response of API, client applications will need to generate an OTP for the mobile number using API call. Respective business applications must retrieve the OTP from the use and submit it when making the Bulk Sign Packages API call. This is done using the "x-otp" header in the request.

6. The signature application needs to call API. This API will sign/sign & share and share multiple documents (both electronic and digital) without displaying the documents to the end user.

7. API will be used to get the status of a specific bulk signing transaction along with the details of document packages that were processed by the previous API call (repetitive call until status becomes COMPLETED).

8. Finally, after signing, the API can be used to retrieve the verification response.

• Introduction

• How it works?

• Place the Policy Document in SigningHub Directory

are similar to the initials, but they are done on behalf of someone else. In-person signatures can be carried out by freehand drawing, text-filling or image upload (the same way a signature is added). When you receive a document with in-person fields assigned to you, then you need to fill in all such fields before signing. This is to witness that the document was signed in the presence of configured persons or on behalf of all of them. Similarly, a meeting host can also provide device control to the (in-person) signers, and get their signatures in his/her presence. Once you are done with in-person signatures, you can sign the document.

Add your in-person signatures

Introduction

SigningHub supports local signing through unique RUT values that are exclusively assigned to each user. The users who wish to use the RUT based Go>Sign signing, need to modify the appsettings.Production.json file. The Go>Sign Desktop app has to be installed and should be running on your machine. Your RUT-based certificates that you want to perform signatures with, having the Subject Alternative Name value, must also be installed on your local machine. SigningHub supports the latest version of the Go>Sign Desktop app.

Introduction

SigningHub supports performing server-side signing with eID Easy. eID Easy provides a simple API for Qualified Electronic Signature (QES) methods, Advanced Electronic Signature (AES) methods, and strong customer authentication for Remote Signing Service Providers that do not support the CSC interface.

Introduction

SigningHub supports local signing through the Go>Sign Desktop app. The Go>Sign Desktop app has to be installed and should be running on your machine. The certificates that you want to perform signatures with should either be installed on your local machine, or be stored in the HSM token attached to your machine, based on the configurations of your Go>Sign profile. SigningHub supports the latest version of the Go>Sign Desktop app.

Introduction

SigningHub allows users to sign via a signature pad. It involves integrating a specialized device that electronically captures handwritten signatures. This integration is seamless within the SigningHub platform, ensuring a straightforward process for users. Once integrated, users need to make the necessary configurations and connect the signature pad to their computer or tablet, typically via USB or Bluetooth to perform the signatures. While the user writes their signature on the pad using a stylus or pen-like tool, the signature's unique characteristics (such as shape, pressure, and speed) are recorded digitally. SigningHub then applies this captured signature to the document, ensuring it remains secure and legally binding.

How it works?

1. Configure a connector, in SigningHub Admin.

2. Add the connector to the service plan.

3. Configure the signature pad in the user role.

4. Set the signature pad as the default method.

Configure a Connector in SigningHub Admin

Make the following configurations to a connector in SigningHub Admin:

1. In the "Basic Information" section, choose "Signature Pad" as the "Provider".

1. In the "Details" section, fill in the required fields.

Add Connector to a Service Plan in SigningHub Admin

Make the following configurations to a service plan in SigningHub Admin:

1. In the "Signature" section of the service plan, enable the "Enable the Signature Pad to capture hand signature images while signing" option and add the earlier configured connector, as shown below:

Configure Signature Pad in a User Role in SigningHub Web

Make the following configurations to a user role in SigningHub Web:

1. Against your user role, in the "Signature Appearance" tab, enable the Signature Pad option.

Set Signature Pad as the Default Method in SigningHub Web

Make the following configurations to 'My Settings' in SigningHub Web:

1. Against your 'Settings', in the "Signature Preferences" tab, set Signature Pad as the default hand signature method for Web Browsers.

Signing via Signature Pad

To perform signatures via a Signature Pad, follow the below-mentioned steps:

1. From the document listing, open a document having a signature field that you want to sign.

2. Double-click on the signature field, and select a Signing Server for performing signatures.

3. Upon selecting a signing server, the browser will show a pop-up to connect the Signature Pad device. Click on the "Connect" button to connect the signature pad.

Signing Behavior w.r.t Signature Appearance

The signing behavior of the system with respect to whether the signature appearance and the logo have been configured against a signing server, in the SigningHub Admin, is as below:

Signing Behavior w.r.t Signature Appearance

The signing behaviour of the system with respect to whether the signature appearance and the logo have been configured against a signing server, in the SigningHub Web, is as below:

Introduction

SigningHub allows you to add electronic seals in a workflow. Electronic Seal (eSeal), Advanced Electronic Seal (AdESeal), and Qualified Electronic Seal (QESeal) are the levels of assurance available for an electronic seal. Adding electronic seals will consume signatures quota of your (document owner's) account. Adding an electronic seal is subject to your SigningHub license, service plan configuration and the assigned enterprise user role.

Introduction

SigningHub supports performing local side signing with Trust1Connector (T1C). For this, SigningHub needs to be registered with the T1C platform, and a T1C connector needs to be created in SigningHub to allow SigningHub to connect with the T1C app. The T1C app has to be installed on your local machine, and the related HSM is attached to it while signing, or the system certificates must be available within the local keystores. Also, you should have full rights to the Trust1Connector service running on your machine. SigningHub will prompt you if any of the prerequisites mentioned above are missing. T1C provides a solution to read the hardware tokens with minimum footprint and installations. It can interact with the hardware tokens by using javascript APIs which are implemented in SigningHub for local signing. SigningHub also supports T1C TrustStore for signing documents using locally stored certificates from keystores on Windows and macOS. (The support for TrustStore requires T1C JS SDK version 3.8.5 or later.) T1C can be used as an alternative to the Go>Sign Desktop for local signing. SigningHub supports the T1C SDK v3.8.6.