System Nomenclature

Terminologies

Description

SigningHub Cloud

SigningHub Cloud is the hosted cloud services for document approval workflows, advanced digital signatures and document status tracking. It allows "Individual" and "Enterprise" level subscriptions against the predefined service plans. 

SigningHub Enterprise (on-premises)

SigningHub Enterprise (on-premises) is a license based privately hosted cloud services for document approval workflows, advanced digital signatures and document status tracking. In addition to the public cloud features, it offers advanced product level configurations where administrators can manage accounts, create custom service plans, configure desired service connectors, signing methods, billing details, integrate and embed with 3rd party business applications and can tune many more system provisions through an Admin console. In short giving you complete control on customizing the SigningHub web interface for large enterprises.

Individual Account

A SigningHub subscription acquired for an individual entity is called an individual account. The individual subscriptions have limited features as compared to enterprise subscriptions.

Enterprise Account

A SigningHub subscription acquired for any group of people (team) or organization is called an enterprise account. An enterprise account is features enriched subscription and comprised of enterprise owner, enterprise admin(s) and enterprise user(s).

Certified Signature

Signatures that certify a PDF are called certified signatures. A certified signature attests to the contents of the document and allows the signer to specify the types of changes allowed for the document to remain certified.

Certified Document

A certified document is one that has a certified signature applied by their document owner, when the document is ready for use. The document owner specifies what changes are allowed for the recipients, from the following permitted modifications:

  • Certify with no changes
  • Certify with form filling
  • Certify with form filling and annotations

Payment Type

SigningHub supports two types of payment:

  • "Regular" payment type is opted when payment is to be made on regular basis (monthly/ annually) against a continuous service plan. In case of monthly payment, the payment is made automatically on 31st day from the subscription date, and the signature pack is reset. Similarly, in case of annual payment, the payment is made automatically on 366th day from the subscription date, and the signature pack is reset accordingly. Moreover, special discounts are also offered on annual payments.
  • "Pay As You Go" payment type is opted when payment is to be made after consuming the allowed signature pack.

Template

The workflow settings configured on a document is called a template. The templates are created to reuse the same configurations on other documents as well. Based on your service plan, a template may save the following information: 

  • Configured recipients
  • Collaboration order (the sequence in which users are required to sign/ review/ update the document)
  • Signing fields and their respective positions
  • Form fields used (if any)
  • Initials and In-persons used (if any)
  • Workflow type (sequential or parallel)
  • Allowed permissions (downloading, printing, password, access duration, and legal notice) 

Workflow

Workflow in SigningHub is a document approval process (i.e. signing, reviewing, updating) that is configured by the document owner. It is also called document preparation. A workflow can be of three types:

  • Serial - A single copy of document is circulated among all the signers in the defined (linear sequential) order, and collects all the signatures on it. Each signer can sign the document on his turn.
  • Parallel - A single copy of 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 document are produced.

Local Signing

In Local (client-side) signing, the signing keys (crypto keys required for digital signature creation) are held in local keystore or in smartcards or in USB-crypto tokens. For this, Go>Sign Desktop application is required on the system along with correct drivers of the installed devices. 

Mobile Signing

In Mobile signing, the signing keys (crypto keys required for digital signature creation) are held on the user's mobile device. For this, a supported mobile signing app is required to use this feature.

Server-Side Signing

In Server-Side signing, the signing keys (crypto keys required for digital signature creation) are held at server end. These keys can be used through any modern browser of Windows, Mac OS X, iOS, Andriod or other devices/ tablets for signing at server end. For this, an SMS OTP authentication can also be enabled, by which the authentication password will be directly sent on your mobile device at the time of signing for confirmation.

One Time Password (OTP) Security

OTP is a security system that requires a new password every time a user authenticates themselves, thus protecting against an intruder replaying an intercepted password. If this option is enabled in the user billing plan then after clicking on the "Sign" button, an OTP will be sent to the users mobile number that was provided at the time of registration.

Group Signing

The group signing feature enables you to send a document to a group of users (e.g. Sales, HR etc), and allows any group member to sign the document on behalf of all the group members. In such a scenario, when a group member opens the document, it (the document) becomes locked (read only) for other group members, and hence allowing only one signer (who opened it first) to sign the document.

Group Approving

The group approving feature enables you to send a document to a group of users (e.g. Sales, HR etc), and allows any group member to review/ approve the document on behalf of all the group members. In such a scenario, when a group member opens the document, it (the document) becomes locked (read only) for other group members, and hence allowing only one reviewer (who opened it first) to review the document.

Group Updating

The group updating feature enables you to send a document to a group of users (e.g. Sales, HR etc), and allows any group member to edit/ update the document on behalf of all the group members. In such a scenario, when a group member opens the document, it (the document) becomes locked (read only) for other group members, and hence allowing only one editor (who opened it first) to update the document.

Initials Fields

Initials fields are the short form of signature and are associated with the recipients (i.e. signers, reviewers, meeting hosts, and editors). In this case, the digital signatures are not embedded. Initial fields can be filled in by hand drawing, text filling or image uploading (the same as when signing a field), and they are added as annotations in the PDF. However, the initials feature is package based and is available for configuration, if it is included in your service plan. 

In-Person Fields

In-person signatures are similar to the initials fields. They are associated with the signers and meeting hosts only, and are usually done on behalf of someone.In-person signatures are added as annotations in the PDF. They can also be used as witness digital signatures, if they are generated by using a witness certificate. The people to configure for in-person signatures don't need to be the registered users of SigningHub. However, the in-person feature is package based and is available for configuration, if it is included in your service plan.

Workflow history

The complete list of activities performed on a shared document with respective details, are maintained in workflow history. The "Workflow History" option is available to the respective document owner only. 

Attachments

Any type of file that is added in the document as an annotation is called an attachment. The "Attachment" option is available to the respective document owner only. Once added, the attachments are available to all the recipients who can view and download them.

Legal Notice

Legal notice is comprised of certain terms and conditions that must be agreed by the (configured) recipients before signing/ reviewing/ updating a workflow document.

Password Policy

Password policy binds the enterprise users to use the same combination of characters for your account password, as defined by the enterprise admin, i.e. password length (total number of characters), number of alphanumeric characters in the password, and number of special characters in the password.

Tight Integration

In the tight mode of integration the users interact with your web application and present the document or form as an iFrame/widget within your application’s webpage. There is no website redirection and the user’s browser address bar doesn’t change. Your users can then view the document, fill-in any form fields and create their digital signature while staying on your site. Tight integration is suitable for ECM, CRM or ERP web applications or portals, where a user already logs in to interact in a defined way.

Loose Integration

The loose mode of integration is where your business application initiates the sign-off workflow, but the end users actually interact with SigningHub when its their turn to sign the document, instead of logging on to your business application. This loose mode of integration is useful in situations where external users are required to sign documents and they do not have access to your internal business application web interfaces. For more details, contact support@signinghub.com

Document Owner

Any SigningHub user who initiates the document workflow, is called a document owner. In addition to performing other activities, a document owner can exclusively view the "Document Logs" and "Attachments" options in their documents.

Recipient

The actual user who has been sent a document for collaboration (signing, reviewing, updating, or hosting) by the document owner, is called a recipient. A recipient may or may not be a registered SigningHub user at the time of document sending.

However, in order to collaborate with the document workflow, s/he will have to register with SigningHub. Based on your document approval requirements, a recipient can be assigned 4 different roles, i.e.:

  • Document Signer:

Being a signer, the recipient needs to sign a document. As per the workflow configuration, this signature can either be electronic or digital. After signing in the assigned signature field, a signer has to click the "Finish" button to complete the document signing. Alternatively s/he may use the "Decline" option to refuse it, or use the "Delegated" option to assign their role to someone else.
Whenever a digital signature is made by any signer, the signature quota of the respective document owner's account will be consumed. Moreover, a signer should also fill in the assigned form fields, initials, and/ or in-persons fields (if any) before signing.

  • Document Reviewer:

Being a reviewer, the recipient needs to approve a document by clicking the "Approve" button. Alternatively s/he may use the "Decline" option to refuse it, or use the "Delegated" option to assign their role to someone else. Reviewing does not involve any signing activity. Moreover, a reviewer should also fill in the assigned form fields, and/ or initials (if any) before reviewing.

  • Document Editor:

Being an editor, the recipient needs to update a document by clicking the "Submit" button. Alternatively s/he may use the "Decline" option to refuse it, or use the "Delegated" option to assign their role to someone else. Editing does not involve any signing activity. An editor should also fill in the assigned form fields, and/ or initials (if any) before updating.

  • Meeting Host:

Being a meeting host, the recipient  needs to facilitate the document signing process for the configured in-person signers. A host can give his/her device control to the (in-person) signers, and get their signatures in his/her presence. After getting all the signatures, a meeting host has to click the "Finish" button to complete the document hosting. Alternatively s/he may use the "Decline" option to refuse it, or use the "Delegated" option to assign their role to someone else.
Hosting itself does not involve any signing activity. However, a host should also fill in the assigned form fields, and/ or other information fields before finishing.

  • Send a Copy:
    When the "Send a Copy" role is selected for a recipient, SigningHub emails the most recent copy (at that stage of workflow) of document to the recipient as an email attachment. The document copy is auto sent (on its turn) and does not require any human intervention. 
  • Electronic Seal
    This user role only appears against an electronic seal added to the workflow. This user role is disabled and can not be updated.



See Also