Skip to end of metadata
Go to start of metadata

Which document types are supported in SigningHub?

SigningHub supports a wide range of commonly used document file types and converts them to the PDF files before signing, see details. It also optionally supports to sign Microsoft Word documents in their native XML format, see details. 

Which signature types are supported in SigningHub?

You can create Electronic Signatures, Digital Signatures (i.e. PAdES Part 2 (Basic), PAdES Part 3 (Enhanced), and PAdES Part 4 (Long term)), and EU Qualified Signatures in SigningHub with locally held and server held signing keys. SigningHub also supports the signing of Microsoft Word documents, see details.

What are the machine requirements to sign documents?

There is no hard and fast hardware requirement for document signing. You need any of the available modern browser and that's it. If you intend to use a smart card reader or cryptographic USB token to sign, then ensure that Go>Sign Desktop application is installed on your machine. Find out the compatibility level of your machine. 

Which browsers does SigningHub support for signing? 

All the modern browsers are supported. For more details, check system requirements page.

What is the difference between eSignature and Digital Signature?

An electronic signature (eSignature) can just be an image of your freehand signature or typed name with other details that can easily be copied and reused by others. While a digital signature is an encrypted form of electronic signature that is produced and backed by strong PKI techniques, and hence cannot be reproduced by anyone, see details. 

What kind of restrictions can be applied to a shared document?

The document owner can configure certain restrictions on recipient level, before sharing a document in the workflow. In this way, each recipient can be exclusively addressed with respect to document restrictions. These restrictions are related to:

  • Allowing/ disallowing document printing permissions
  • Allowing/ disallowing document downloading permissions
  • Allowing/ disallowing permissions to add text fields in the document
  • Allowing/ disallowing permissions to change the recipient
  • Allowing/ disallowing permissions to certify the signatures
  • Allowing/ disallowing document attachments and merging permissions
  • Allowing/ disallowing document accessing permissions via password/ OTP/ specific duration
  • Allowing/ disallowing recipient change permissions during workflow
  • Attaching legal notice with the document and restricting signing activity without agreeing to it

For more details, click here if you are using SigningHub v7, or click here if you are using any older version of SigningHub.

What is the workflow?

A workflow manages the document flow from one recipient to another, till the signing process gets completed. In SigningHub, it is a document approval process (i.e. signing, reviewing, updating) that is configured by the document owner. A workflow can be of four types:

  • Sequential - A single copy of the document is circulated among all the signers in the defined (linear) order, and collects all the signatures on it. Each signer can sign the document on his turn.
  • Parallel - A single copy of the document is circulated among all the signers in a parallel order, and collects all the signatures on it. Any signer can sign the document in any order.
  • Individual - Each signer is sent an exclusive copy of the document to sign/ review, and multiple signed copies of the document are produced. 
  • Custom - A single copy of the document is circulated among all the signers in mixed 'sequential and/ or parallel' order as specified in the workflow, and collects all the signatures on it. 

For more details, click here if you are using SigningHub v7, or click here if you are using an older version of SigningHub.

What are all these document statuses? 

SigningHub maintains different statuses (i.e. Draft, Pending, Signed, Declined, etc.) of a document to determine its real-time workflow progress, see details. 

What type of email addresses are acceptable in the registration process of SigningHub? 

SigningHub supports valid email addresses, or you may also use your personal ID (i.e. Salesforce, Dynamics CRM, SharePoint, Entrust IdentityGuard, AET ConsentID, etc.) for registration. In case of an on-premise deployment, legitimate domains can be defined in the SigningHub license file to restrict the users' registration to the enlisted domains only.

What is meant by a sequential workflow?

In a sequential workflow, a single copy of the document is circulated among all the signers in the defined (linear) order, and collects all the signatures on it. Each signer can sign the document on his turn.

What is meant by a parallel workflow?

In a parallel workflow, a single copy of the document is circulated among all the signers in a parallel order, and collects all the signatures on it. Any signer can sign the document in any order.

What is meant by an individual workflow?

In an individual workflow, each signer is sent an exclusive copy of the document to sign/ review, and multiple signed copies of the document are produced. 

What is meant by a custom workflow?

In a custom workflow, a single copy of the document is circulated among all the signers in the defined mixed (sequential and/ or parallel) order.

What is the difference between eSignature and witness eSignature?

An eSignature (electronic signature) is used to indicate a person’s consent to sign. It can be a typed name, scanned image of a handwritten signature or drawn in real-time on a signature tablet etc. and is added as a simple annotation in the document. eSignatures by themselves do not provide authentication of the signer or protect the document from change.

However, a witness eSignature is an electronic signature that is generated by using a digital witness certificate available on the server. The availability of witness eSignature feature is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your service plan.

Do you provide onsite deployment of SigningHub as my company policy stops us pushing documents to 3rd party servers? 

Yes, we do. This is a clear difference between SigningHub and other signing solutions. We'll guide you for the on-premise deployment process, and also provide first-class post-deployment support. Contact sales@signinghub.com for more details on this. 

How does the password based restriction affect the document security?

The password based restriction can improve workflow security, and may further enhance the privacy level. When configured, the recipient cannot open the document without specifying the preconfigured password. However, the document opening password can be separately communicated to the concerned recipient, by any other communication channel (i.e. phone, email etc.). For more details, click here if you are using SigningHub v7, or click here if you are using an older version of SigningHub.

  • No labels