Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
To configure your enterprise profile:
Login with your enterprise admin credentials.
Click "Configuration" and click on "Enterprise Information" under About options in Enterprise Administration section.
Click on "Edit" button.
Specify your information as required and click "Save changes" button.
See the below table for fields description:
SigningHub enables you to manage (Add, Edit, and Delete) a list of enterprise contacts to help make sending documents even easier. These enterprise contacts are available to all the enterprise users within your enterprise, when they need to add recipients in a and/or in a . Also, when a new enterprise user's account is activated, s/he is automatically added in the enterprise contacts by SigningHub.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Contacts" under People options in Enterprise Configurations section.
Click "Add a contact" button on Contacts screen.
Fill the required information in the "Add a contact" dialogue and submit.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Contacts" under People options in Enterprise Configurations section.
Select the desired contact and click "Edit" button in right panel.
Fill in the desired information in the "Edit Contact" dialogue and submit.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Contacts" under People options in Enterprise Configurations section.
Select the desired contact and click "Delete" button in right panel.
Click "Delete" in confirm dialogue.
The mobile number field against a contact is an optional field.
SigningHub enables you to manage (Add, Edit, and Delete) enterprise groups for the , , and/ or purposes. These enterprise groups are available to all the enterprise users within your enterprise, when they need to add recipients in a and/or in a .
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Groups" under People options in Enterprise Configurations section.
Click "Add group" button on groups screen.
Provide "name" and "description" and click "Add member" button.
Enter name or email in the dialogue and after selecting the required contact, click "Add member".
Click "Save new group" button.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Groups" under People options in Enterprise Configurations section.
Select the desired group and click "Edit" button in right panel.
Change the desired information and/or Add or remove member.
Click "Save changes" button.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Groups" under People options in Enterprise Configurations section.
Select the desired group and click "Delete" button in right panel.
Click "Delete" on confirm dialogue.
Field | Description |
---|---|
Enterprise Name
Field to specify your enterprise name. The specified name should be unique throughout SigningHub, as it will be used to identify your enterprise.
Enterprise URL
Field to display a unique URL for your enterprise. The first part of URL is hardcoded as laid out by the SigningHub Admin. You can add your enterprise name in the second part to form a complete URL for your enterprise, being displayed under this field. You can then share this URL with your enterprise users so that they may see the branded enterprise interface right from the login screen. See how to brand your enterprise account in SigningHub.
Account Owner
Field to choose the owner of your enterprise. SigningHub will list all the users in this drop down for whom the "Enterprise Profile" access has been enabled in their role, see details.
Account Owner's Phone Number
Field to display the mobile number of selected account owner from their personal SigningHub profile. This number will be used to send OTP authentication codes on owner's mobile device, if OTP authentication is enabled in your service plan. By default, the specified number is displayed partially masked to comply with the GDPR policy. Click to view the complete number. If you think the owner's mobile number needs to be updated, ask him to go to My Settings>Profile and edit the "Mobile Number" field as required.
Support Email
Specify the email address for your enterprise users, on which they can send their support queries, i.e. enterprise@mysigninghub.com. By default, this field will be empty. This is an optional field.
SigningHub records high-level activities for each Enterprise Settings change along with the particular date and time stamps. The detailed insight is useful to provide an effective audit trail for monitoring any setting change in an Enterprise account. These logs will be available to those enterprise users/ administrators for which the "Enterprise Logs" option is enabled in their role.
In this regard, the following activities are logged:
When you update enterprise profile
When you change a user role
When you delete a user
When you invite a user
When you import a CSV file to invite users
When you resend an invitation to a user
When you delete an invitation
When you register a single user
When you register bulk users
When you update Active Directory user settings
When you add a new role
When you update an existing role
When you delete an existing role
When you clone an existing role
When you add an enterprise contact
When you update an enterprise contact
When you delete an enterprise contact
When you import a CSV file to add enterprise contacts
When you add a new enterprise group
When you update an existing enterprise group
When you delete an existing enterprise group
When you add an enterprise template
When you update an enterprise template
When you delete an enterprise template
When you clone an enterprise template
When you upload/ add a document in enterprise library
When you update a document from enterprise library
When you delete a document from enterprise library
When you add an electronic seal
When you update an electronic seal
When you delete an electronic seal
When you disable two factor authentication (2FA)
When you regenerate two factor authentication (2FA) Recovery Codes
When you update a notification email
When you update a notification email content
When you reset a notification email to default
When you update application integration settings
When you update report settings
When you update document settings
When you add an enterprise legal notice
When you update an enterprise legal notice
When you delete an enterprise legal notice
When you add a certificate filter
When you update a certificate filter
When you delete a certificate filter
When you enable your enterprise user
When you disable your enterprise user
When you update the enterprise default settings
When you update enterprise branding
When you update webhooks
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Logs" under About options in Enterprise Configurations section.
Click "Next" to view your older activity logs. The system will keep fetching the records accordingly. You can also view the associated information of each activity by clicking the respective "Activity".
You can search the enterprise logs on the basis of the relevant "User Name" or "User Email ID" from the top right "Filter".
In case the enterprise logs are in bulk and its hard for you to reach out the exact instance, you can use the "Advanced Search" option. This will enable you to input multiple parameters to retrieve the exact record.
Click "Advanced search" button on top right of the grid.
Specify the available information in the respective fields in the dialogue and click the "Advanced search" button. The system will retrieve the enterprise logs by incorporating all the input parameters in the search.
You can register your enterprise users in bulk through a CSV file. The CSV file must have the valid email addresses of the contacts. SigningHub supports three different types of email headers (i.e. Primary Email, E-mail Address, and Email Address) to pick up the email addresses from a CSV file. This is a smart way for the enterprise admins to directly register multiple users into their enterprise account through a single click, without even following the default registration and activation steps. Moreover, you can also enable/ disable the system access of your enterprise users as required.
User Status | Description |
---|---|
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
Click "Bulk register" button.
Select the role for all the users to be registered. The default role is automatically selected for the new registrations, change it as required.
From the "Send Email" field, choose when to send the notification email to the newly added user:
From the "Send Email" field, choose when to send the notification email to the newly added user:
None: select this option when you want the user to be auto activated without receiving any email. This option is recommended when the user needs to use an external IDP (i.e. Active Directory, Salesforce, Linked-in, etc) for system authentication.
Send Registration Email: select this option when you want the user to be auto activated without receiving the activation email. Only the registration email will be sent (to the user) that contains the information like Enterprise Admin name who has registered the user, and the Enterprise name in which the user has been registered. This option is recommended when the user needs to use an external IDP (i.e. Active Directory, Salesforce, Linked-in, etc) for system authentication.
Send Activation Email: select this option when you want the user to receive the activation email and activate their account through it. This option is recommended when the user needs to use the SigningHub ID for system authentication.
Drag/Drop or select the required csv from system. All those users (with valid email addresses in the CSV file) that are not available in system, or available in system as guest, or have been marked as deleted, will be registered and auto activated in your enterprise with the enabled SigningHub access.
Click on "Submit" button.
There are multiple ways to get a CSV file. You can create a CSV file using any word processing, database, spreadsheet or text edit applications. When creating a CSV file, the first row must be the header row that shows the field names for the file. Each subsequent row can then represent a unique user email id along with the user's names (i.e. first name and last name). A CSV file should contain the following information:
"Email Address" to input user's email id. It is a mandatory column header.
"Last Name" to input user's last name. It is an optional column header.
"First Name" to input user's first name. It is an optional column header.
You can also export your contacts (in a CSV file) directly from Outlook, Thunderbird, or any other email service provider. Since SigningHub is mainly concerned with the email column header of a CSV file, therefore three types of headers are supported, i.e. Primary Email, E-mail Address, and Email Address.
You can edit any content inside a CSV file as required.
In case the contact names are specified in a CSV file (i.e. First Name and/ or Last Name), they will be populated accordingly in the name fields of a contact.
In case a contact name is not specified in any name field, then the contact username (portion of email address before the "@" symbol) will be shown as contact name.
The rest of the column headers inside a CSV file are not related to SigningHub, so they will be ignored when you import the file.
The activated users can also log into SigningHub with their non-SigningHub Ids, if it is allowed in their subscribed service plan.
When the newly registered users try to log into SigningHub by using the SigningHub IDs, they will be sent the activation emails to activate their accounts.
When users are registered via CSV file, the user certificates are generated as per the user names, i.e. User name and their certificate name will be the same. However these names (User and Certificate) can be updated later as required.
The CSV file being used for registering the enterprise users in bulk must have the valid email addresses of the contacts. SigningHub supports three different types of email headers for a CSV file, i.e. Primary Email, E-mail Address, and Email Address. You can export your contacts (in CSV) from Outlook, Thunderbird, or any other email service provider that supports these email headers.
If the CSV file being used for registering the enterprise users in bulk has the Cloud Signature Consortium (CSC) User ID of the contacts, it will be extracted, given that the SigningHub supported header is used in the CSV file. SigningHub supported header for Cloud Signature Consortium (CSC) User ID is "CSC_ID".
While exporting contacts from different email clients (like Microsoft Outlook and Gmail) you often end up having different column headers for the same field. For example, Gmail has "Primary Email" for the Outlook's "Email Address" column header. You do not need to rename the CSV headers to conform because SigningHub supports such variations in the CSV column headers. These variations are correctly mapped with the SigningHub fields. The following table illustrates which SigningHub field maps with the corresponding CSV header along with supported variations. Note: Other than "Email" field, all the fields are optional.
Against the "Home Country" header specify the countries of the users that shall be saved in the user's profile and signing details. If a country has not been specified against a user, it is fetched from the Global Settings > Default Locale.
SigningHub allows you to import contacts in bulk using a CSV file. The file must have the valid email addresses of each contact. This is a smart way for individuals and enterprise users to add multiple contacts into SigningHub through a single click. SigningHub supports:
The "Primary Email", "E-mail Address", and "Email Address", to read the email address from the CSV file.
The "Mobile Number" header to read the mobile number of the contacts.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Contacts" under People options in Enterprise Configurations section.
Click "Bulk contacts" button.
Drop or upload csv file to "Bulk contacts" dialogue and submit.
All the contacts (with valid email addresses) that do not previously exist in your SigningHub account, will be added from the CSV file.
There are multiple ways to get a CSV file. You can create a CSV file using any word processing, database, spreadsheet or text edit applications. When creating a CSV file, the first row must be the header row that shows the field names for the file. Each subsequent row can then represent a unique user email id along with the user's names (i.e. first name and last name).
A CSV file should contain the following information:
"Email Address" to input user's email id. It is a mandatory column header.
"Last Name" to input user's last name. It is an optional column header.
"First Name" to input user's first name. It is an optional column header.
"Mobile Number" to input user's mobile number. It is an optional column header.
You can also export your contacts (in a CSV file) directly from Outlook, Thunderbird, or any other email service provider. Since SigningHub is mainly concerned with the email column header of a CSV file, therefore three types of headers are supported, i.e. Primary Email, E-mail Address, and Email Address.
You can edit any content inside a CSV file as required.
In case the contact names are specified in a CSV file (i.e. First Name and/ or Last Name), they will be populated accordingly in the name fields of a contact.
In case a contact name is not specified in any name field, then the contact username (portion of email address before the "@" symbol) will be shown as contact name.
The rest of the column headers inside a CSV file are not related to SigningHub, so they will be ignored when you import the file.
The CSV file being used to import contacts in bulk must have the valid email addresses of the contacts. SigningHub supports three different types of email headers for use in a CSV file, i.e. Primary Email, E-mail Address, and Email Address. You can export your contacts (to a CSV file) from Outlook, Thunderbird, or any other email service provider that supports these email headers.
To populate the contact's name field, SigningHub looks for the name fields within the CSV file, i.e. First Name and Last Name, and combines them. If the contact name is not specified, then the contact username (portion of email address before the "@" symbol) will be shown as contact name.
To populate the mobile number field, the "Mobile Number" header is supported with in the CSV file, for reading the mobile number of the contacts.
SigningHub facilitates you to directly register any user into your enterprise without even following the default registration and activation steps. Once registered, you can enable/ disable the system access of your enterprise users as required. You can search the registered useers on the basis of their name/ email, and can also sort them in ascending or descending order as required.
User Status | Description |
---|---|
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
Click "Add a user" button.
Specify Name, Common Name, Email, Role, Mobile Number, Job TItle, Company Name, Language, Country, Remote Authorisation Signing ID, Cloud Signature Consortium (CSC) User ID, CSP Signing ID, Send Email, and the National ID of the enterprise user in the provided fields. Only the Name, Email and Common Name fields are the mandatory ones. The default role is automatically selected for the new registration, change it as required. Common Name is used for the certificate name that is issued against each registered user. The issued certificate identifies the user and their enterprise.
From the "Send Email" field, choose when to send the notification email to the newly added user:
None: select this option when you want the user to be auto activated without receiving any email. This option is recommended when the user needs to use an external IDP (i.e. Active Directory, Salesforce, Linked-in, etc) for system authentication.
Send Registration Email: select this option when you want the user to be auto activated without receiving the activation email. Only the registration email will be sent (to the user) that contains the information like Enterprise Admin name who has registered the user, and the Enterprise name in which the user has been registered. This option is recommended when the user needs to use an external IDP (i.e. Active Directory, Salesforce, Linked-in, etc) for system authentication.
Send Activation Email: select this option when you want the user to receive the activation email and activate their account through it. This option is recommended when the user needs to use the SigningHub ID for system authentication.
​National ID refers to a RUT/ RUN/ eID or any unique identifier of a user to identify them in SigningHub. This is an optional field and is used in addition to the user email ID. When specified, this identification will be available on the following areas:
The "General" section of User Profile
The "Registered Enterprise Users" screen
The Workflow screens related to recipient, i.e. Add Recipient, Update Recipient, Replace Recipient, etc.
The Template screens related to recipient adding and updating
The document viewer
The "Delegate Signing" screen
The "Advance Search" dialog of Enterprise Users
The activated users can also log into SigningHub with their non-SigningHub Ids, if it is allowed in their subscribed service plan.
The user name and their certificate name can be the same or different as required.
When the newly registered user tries to log into SigningHub by using the SigningHub ID, they will be sent an activation email to activate their account.
Two factor authentication (2FA) strengthens access security by requiring two methods to verify your identity. SigningHub allows you to configure a Time based One Time Password (TOTP) under two factor authentication (2FA). A Time based One Time Password (TOTP) is a temporary passcode generated by an algorithm that uses the current time of day as one of its authentication factors. Time based One Time Passwords provide additional security as even if a user's traditional password is stolen or compromised, an attacker cannot gain access without the TOTP, which expires quickly. SigningHub allows the Enterprise Admin the option to reset the two factor authentication (2FA) configured against an enterprise user. The "Reset 2FA" option will only appear if the "Enable Time based One Time Password (TOTP)" option is enabled in the user's service plan, and the user has configured two factor authentication (2FA).
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
Click "Reset password" button.
Click "Yes" from the 2FA dialogue appear.
SigningHub records the high-level activities of each user account along with particular date and time stamps, and other details to provide an effective audit trail. There are mainly five types of activities that are logged against each user, i.e. Account/ User, Document, Billing, Settings and Enterprise related activities, see . You can view these activities of each user within your enterprise.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
Expand the "Activity" tab. Click on any and you can see the details in right panel.
SigningHub allows you to configure a specific quota against each system resource/ service for your enterprise users on individual basis. This is useful to restrict them from abusing the system resources as allowed in your enterprise service plan. In this way, you can prevent your enterprise from being hijacked by a few individuals consuming the available resources.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
Expand "Usage and Limits" tab and you can configure the limits in numbers.
Click "Save changes" button.
"Simple Electronic Signatures" constraint option will only be displayed, if the "SIMPLE_ELECTRONIC_SIGNATURES" module enabled in the license.
In case a limit has been set for "Signatures" but unlimited has been checked against each level of assurance, the user will be allowed to use each level of assurance as long as their aggregate is less than the limit set for "Signatures".
The limit set for each level of assurance can not be greater than the limit set for "Signatures".
SigningHub enables you to manage (Invite, register, update role, delete, change password, enable and disable, view activities and statistics) users' registrations for your enterprise. You can directly register your enterprise users, or may also invite them through emails. The users accepting your invitations are then brought into your enterprise as the registered enterprise users.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
User detail screen will appear with all the information in respective tabs.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
Select the user(s) you want to delete and click "Delete" button in right panel.
A dialog will appear to confirm the user(s) deletion activity.
Click the "Delete" button without selecting the "Delete user permanently" option to remove the selected enterprise user(s) from your enterprise account. SigningHub will transform these account(s) from enterprise user(s) to individual account(s) with the default (free) service plan.
Click the "Delete" button after selecting the "Delete user permanently" option to purge the selected enterprise user(s). SigningHub will permanently delete these accounts from system along with their transactions.
You can export the enterprise users record to an excel sheet file (xlsx) by clicking "Export to excel" button. The excel sheet file is downloaded to your local Downloads folder.
When a new enterprise user's account is activated, SigningHub adds them in the Enterprise Contacts as well.
When an enterprise user's account is deleted, SigningHub converts the enterprise user account to an individual account with the default (free) service plan.
SigningHub lets you initiate the password changing process of your enterprise users. In this case, a password resetting email is sent to the respective enterprise user, from where they can change their account password.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
Click "Reset password" button.
The respective enterprise user will be sent an email including the password change link. From where they can change their SigningHub account password.
SigningHub does not allow its users to set as password, the following:
Their user account (i.e. Email Address)
The last used password
Their full user name
At times people make typo mistakes while adding user information, or the details may require update after certain time period. SigningHub therefore allows an enterprise admin to edit/ update their enterprise users' information as required. You can edit user name, their mobile number, job title, and company name. Similarly, you can also change the role of your enterprise user anytime in order to update their system access.
Login with your enterprise admin credentials.
Click on "Configuration" in left menu and click "Users" under People options in Enterprise Administration section. Users Screen will appear.
If you want to view further detail of your user, select the user and click "User preferences" button in right panel.
Open "Profile Information" tab and click "Edit" button.
Fill in the detail as required. Since the "Email" field is used as user's SigningHub account ID, therefore it is not editable and is displayed as a read-only field.
Business applications can use this service API to add a certificate for Enterprise Users into their Enterprise account. An enterprise Admin who has permissions to manage enterprise users in this role, can import RAS (Remote Authorization Signing) enabled certificates for signing. Furthermore, the signing certificates appears at signing time (if RAS is enabled under service plan and under intended user's role). The Role dictates things such as allowed signing capacities available to the user.
SigningHub will provide an option to enterprise admin that will allow to add (import) / update / delete user certificates. Management of certificates will only be limited to those certificates that has been imported by Enterprise admin and not the ones which are generated by system. End user will get all signing certificates added by Enterprise admin or by system. Option will only appear if Enterprise has RAS enabled in service plan other than that Enterprise will not be able to manage user certificates.
Open "Add a Signing Certificate" tab and click "Add a Signing Certificate" button.
Fill the required information in the appeared dialogue.
Click "Save changes".
Capacity name should be user-friendly, that could consist of letters and numbers.
Capacity name should not be more than 100 characters.
Capacity name should be unique for each user i.e. capacities added by enterprise admin and provided by Service Plan shouldn't match.
Capacity Alias should be same as of provided in ADSS.
All conditions mentioned above must be fulfilled and needs to be filled by Enterprise Admin only.
The Document Preferences tab lets you configure documents related settings in a role. From here you can set the privileges for the document owners and recipients (within your enterprise) registered with this role, and may also configure document related provisions available within integration mode (i.e., iFrame). The concept of has been introduced which allows delegating your document processing authority to a group of users, configure it as required. It also provides a team working environment, where the peers have the same set of privileges inside a space and can process the team documents accordingly.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Document Preferences". Select the user settings check boxes and their respective granular access as required.
Click "Save changes".
See the description in the "Document Preferences" table below.
The enterprise admin who is willing to upload and share documents on behalf of their enterprise users, must have the "Application Integration" rights in their assigned role.
The "Template Applying", "Package Renaming", "Document Renaming", "Documents Merging", and "Documents Managing" options will not be available in the integration mode (i.e., iFrame), irrespective of their role settings.
When you update a role in a production environment, the saved changes are applicable to the related users on their next login.
The availability of "Bulk Signing and Sharing" provision is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your service plan.
In the "Level of Assurance" field under the "Allowed Signature Fields" section, the names of the Levels of Assurance are displayed as configured in the SigningHub Admin.
In addition, this field displays all the Levels of Assurance available in the SigningHub Admin. The "Only share with your enterprise contacts and groups" and the "Allow users to only use personal contacts and groups" options can not be checked simultaneously. If either one of the checkbox is checked, and the user tries to check the other one, the system will prompt an error
.
In case the "Allow users to only use personal contacts and groups" checkbox is checked, only personal contacts and groups will be visible to the user while:
Starting a workflow
Changing a recipient
Adding a collaborator for the workflow
Adding a collaborator in the template
Adding a collaborator in the shared space
Configuring delegated signing
Configuring the delegate settings; for the delegator and the gatekeeper
Personal groups
Configuring the personal groups; the system will hide the enterprise dropdown from personal groups.
Configuring the personal contacts; the system will hide the enterprise dropdown from personal contacts.
Configuring post processing
The system will show the user name of a configured contact by checking the email address in the personal contacts, if the contact does not exist in personal contacts, then the system will show, as user name, the name set by the contact itself in their "My Settings".
If the "Set Document Access Authentication for all recipients" option is selected against the document owner's user role, the document owner will not be allowed to share the workflow until "Document Access Authentication" is set for all the recipient in the workflow.
If the "Set Document Signing Authentication for all recipients" option is selected against the document owner's user role, the document owner will not be allowed to share the workflow until "Document Signing Authentication" is set for all the recipient in the workflow.PreferencesPreferences
Field Name in SigningHub | Supported Header in CSV |
---|---|
Field Headers | Description |
---|
User Status | Description |
---|
Please note, the "Role" field will only be editable if you have got the and privileges assigned to your role, otherwise it will be displayed as read-only. If you change the Common Name of a user, their existing certificate will be revoked and a new certificate is generated as per the new Common Name upon signing.
When updating the Country of a user, the updated country will not be reflected in the and .
1- ADSS | 2- Signing Hub Admin > Service Plan | 3 - Signing Hub Web > Enterprise > Users |
---|
Field | Description |
---|
Name
First Name, Middle Name, Last Name (Note: Your CSV may contain any or all of these column headers. In case your CSV has more than one of these column headers, like "First Name" along with "Last Name", SigningHub will concatenate both and map with the "Name" field.)
Email Address, E-mail Address, Primary Email
Mobile Number
Mobile Phone, Contact Number, Phone Number, Mobile Number
Job Title
Job Title
Company Name
Company, Organization
Cloud Signature Consortium (CSC) User ID
CSC_ID
Country
Home Country
Constraint | This header lists all the system resources whose usage limits can be quantified, i.e. Signatures, Simple Electronic Signatures , Storage, Workflows, Document Upload Size, and Templates. |
Allowed | This header lists the blank fields against each system resource (constraint) to define their limits in numbers. The defined number cannot be more than the respective limit as allowed in your enterprise service plan. If you leave any field blank against a particular constraint, SigningHub will allow the maximum limit to it as per the allowed limit in your enterprise service plan. |
Consumed | This header lists the utilized resources against each constraint by this enterprise user. |
Service Plan | This header lists the allowed resources in your service plan against each constraint. |
|
|
|
|
|
Activated & Enabled | This status implies that a user's account is activated and their access is enabled in SigningHub. These users can log into their SigningHub accounts and use the system. |
Activated & Disabled |
Enabled | This status implies that a user has been directly registered by enterprise admin with enabled access in SigningHub (by using the "Send Activation Email" option), however the user has not activated their account as yet. These users need to activate their accounts by following the activation email to start using SigningHub. |
Allow uploading and sharing of new documents | Select this option to allow the document owners within your enterprise (belonging to this role) to upload and share documents with any users (i.e., inside and outside your enterprise). This will enable the "New Workflow" option on their System Dashboard and Document Listing screens. If you keep the "Upload and Share" option deselected, it will restrict the document owners to upload and share documents with other users. However, they can still sign their (personal and received) documents.
|
Manage recipients after sharing a document | Select this option to allow the document owners within your enterprise (belonging to this role) to change the specified recipients after sharing a document. If you keep this option deselected, it will restrict the document owners to change the recipients once a workflow is initiated by them. |
Printing | Select this option to allow the document owners within your enterprise (belonging to this role) to print the documents after initiating their workflows. If you keep this option deselected, it will restrict the document owners to print their workflow documents. |
Download | Select this option to allow the document owners within your enterprise (belonging to this role) to download the documents after initiating their workflows. If you keep this option deselected, it will restrict the document owners to download their workflow documents. |
Manage document attachments and document merging | Select this option to allow the document owners within your enterprise (belonging to this role) to manage their documents attachments and merging, after initiating their workflows. If you keep this option deselected, it will restrict the document owners to manage attachments of their documents or merge their documents once their workflows are initiated by them. |
Recall workflows | Select this option to allow the document owners within your enterprise (belonging to this role) to recall workflows. If you keep this option deselected, it will restrict the document owners from recalling their workflows. |
Allow users to save a workflow as a template | Select this option to allow the document owners within your enterprise (belonging to this role) to save workflows as templates for use later. If you keep this option deselected, it will restrict the document owners from saving workflows as templates. |
View the workflow details and workflow evidence reports | Select this option to allow the document owners within your enterprise (belonging to this role) to view the workflow history and workflow evidence reports of their documents after initiating their workflows. If you keep this option deselected, the document owners will not be able to see these options against their workflow documents. |
Add invisible signatures in the document | Select this option to allow the document owners within your enterprise (belonging to this role) to add invisible signatures in a document. This will add an additional field (i.e., Display) under the "Details" tab of a signature field properties dialog. An invisible signature will not be displayed on a document. However it entails all other verifiable characteristics of e-signing i.e., Time stamping, Certificate Chain, Certificate Status, etc. An invisible signature can be a Digital Signature, Witness Digital Signature or Witness In-Person Signature as configured in a workflow. |
Enforce document access authentication for all the recipients | Select this option to require the document owners within your enterprise (belonging to this role) to set the document access authentication for all the recipients before sharing the workflow. By default, this option is deselected. If you keep this option deselected, the document owners will be able to share the workflow without having to set the document access authentication for all the recipients. |
Enforce document signing authentication for all the recipients | Select this option to require the document owners within your enterprise (belonging to this role) to set the document signing authentication for all the recipients before sharing the workflow. By default, this option is deselected. If you keep this option deselected, the document owners will be able to share the workflow without having to set the document signing authentication for all the recipients. |
Certification options | Select this option to allow the document owners within your enterprise (belonging to this role) to certify the document to restrict the recipients to perform only the specific changes in a document, as the system won't allow them to perform any other changes. If you keep this option deselected, the document owners will be able not be able to certify documents. |
Signature field |
|
In-Person signature field | Select this option to allow the document owners within your enterprise (belonging to this role) to add In-Person signature fields in their workflows. If this option is selected, the "Level of Assurance" and "Default Level of Assurance" mandatory fields will appear for the user to configure. If you keep this option deselected, the document owners will not be able to add the "In-Person Signature" field while preparing workflows. The "Level of Assurance" field allows the enterprise admin to configure the levels of assurance that the document owners are allowed to use for an In-Person signature field. You can either allow specified levels of assurance or allow all available levels of assurance. The drop down list for this field displays the levels of assurance as configured in the service plan. The possible options for this field are:
The "Default Level of Assurance" field defines what level of assurance will be used by default when the document owners drops an In-Person signature field. The system automatically populates this field as per the "Default Levels of Assurance" field, in the service plan. The configured levels of assurance from the "Level of Assurance" field will be listed in the "Default Level of Assurance" drop down list for the enterprise admin to manually configure the "Default Level of Assurance" field. The configuration of this field supersedes the configuration of the "Default Levels of Assurance" field in the service plan. For a new enterprise user under a specific role, the system will pick the configured default level of assurance from this field and set it as the default level of assurance for the user in Personal Settings. |
Initials | Select this option to allow the document owners within your enterprise (belonging to this role) to add initials fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Initials" field while preparing workflows. |
Name | Select this option to allow the document owners within your enterprise (belonging to this role) to add name fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Name" field while preparing workflows. |
Select this option to allow the document owners within your enterprise (belonging to this role) to add email fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Email" field while preparing workflows. |
Date | Select this option to allow the document owners within your enterprise (belonging to this role) to add date fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Date" field while preparing workflows. |
Company | Select this option to allow the document owners within your enterprise (belonging to this role) to add company fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Company" field while preparing workflows. |
Job Title | Select this option to allow the document owners within your enterprise (belonging to this role) to add job title fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Job Title" field while preparing workflows. |
Text field | Select this option to allow the document owners within your enterprise (belonging to this role) to add text fields in their workflows. If you keep this option deselected, the document owners will not be able to add "Text Field" while preparing workflows. |
Text area | Select this option to allow the document owners within your enterprise (belonging to this role) to add text areas in their workflows. If you keep this option deselected, the document owners will not be able to add the "Text Area" field while preparing workflows. |
Radio button | Select this option to allow the document owners within your enterprise (belonging to this role) to add radio buttons in their workflows. If you keep this option deselected, the document owners will not be able to add "Radio Button" while preparing workflows. |
Check box | Select this option to allow the document owners within your enterprise (belonging to this role) to add check boxes in their workflows. If you keep this option deselected, the document owners will not be able to add "Check Boxes" while preparing workflows. |
Add text | Select this option to allow the document owners within your enterprise (belonging to this role) to add text fields in their workflows. If you keep this option deselected, the document owners will not be able to add the "Add Text" field while preparing workflows. |
Attachment | Select this option to allow the document owners within your enterprise (belonging to this role) to add attachment fields in their workflows. If you keep this option deselected, the document owners will not be able to add "Attachment" field while preparing workflows. |
QR Code | Select this option to allow the document owners within your enterprise (belonging to this role) to add QR codes in their workflows. If you keep this option deselected, the document owners will not be able to add QR codes while preparing workflows. |
Proceed automatically upon completion of the mandatory actions by the signer | Select this option to automatically trigger the "Finish" button in a role. When the users belonging to this role will complete the mandatory actions of their collaboration, the "Finish" button will not be displayed on the screen and the process will be concluded automatically from their end. If the "Automatically proceed with workflow upon completion of mandatory actions by signer" option is checked, the "Automatically close the document viewer" option shall appear. Select the "Automatically close the document viewer" sub option to automatically close the document viewer once the signer has performed all the mandatory actions. By default, this option will be unchecked. |
Add comments on documents | Select this option to allow the enterprise users (belonging to this role) to add comments on the workflow documents once their workflows are initiated. If you keep this option deselected, it will restrict them to add comments on such documents. |
Delete documents | Select this option to allow the enterprise users (belonging to this role) to remove documents from their accounts. If you keep this option deselected, it will restrict them from deleting documents from their accounts. |
Perform actions on behalf of enterprise users | Select this option to allow your enterprise admin to upload and share documents, manage recipients, add signature fields and form fields on behalf of the enterprise users belonging to this role, by using the SigningHub API. This is useful in cases where a specific set of users (i.e., Reviewers) are not allowed to upload and share documents on their own (i.e., the "Upload and Share" option is turned off for them), however they can still review the current status of documents and can send their reminders as required. |
Manage shared folders | Select this option to allow the users within your enterprise (belonging to this role) to manage their shared spaces. They can create their own shared spaces for their nominated collaborators, and may also edit and delete these spaces as required. In this way, the nominated collaborators can process the workflows of a shared space documents on behalf of the space owner in their absence. If you keep this option deselected, the users (belonging to this role) would not be able to manage their own shared spaces. However they can still collaborate in the shared spaces of other users, if they are made collaborators in them. |
SigningHub allows the Enterprise Admin to access the enterprise documents, if you want to view your enterprise documents, go to the enterprise documents listing. SigningHub maintains a log of each action being performed on a document along with the respective date and time stamps. The "Workflow Details" dialog which presents the logs of each action being performed consists of two tabs; "Workflow History" and "Workflow Timeline". However, viewing "Workflow Details" is subject to your assigned enterprise user role. These logs are only available to the respective Enterprise Admin.
The following document actions are logged under "Workflow History":
When was the document uploaded by a user
When was the document added from library by a user
When was the document added from cloud by a user
The original format of the uploaded document
When the document was converted to pdf format after upload
When was the document opened by a user
When was the document closed by a user
When was the contact added in the document by a user
When was the comment added in the document by a user
When was an attachment added in the document by a user
When was a text field added in the document by a user
When was a form field filled in the document by a user
When was a form field text updated in the document by a user
When was the document initials were filled by a user
When was the document signed In-person by a user
When was the document signed by a user
The signing capacity with which a user signed the document
The signing reason for signing the document
When was the document shared by a user
When was the document recalled by a user
When was the document approved by a user
When was the document updated by a user
When was the document hosted for in-person signatures by a user
When was the post processing activity done on the document by a user
When was the document declined by a user
When was the document renamed by a user
When was the document deleted by a user
When was the document printed by a user
When was the document added in the library by a user
When was the document downloaded by a user
When was the document template added by a user
When was the document template applied by a user
When was the document workflow completed by a user
When was the document workflow updated by a user
When was the attached legal notice accepted by a user
The following document details are logged:
Who was the document shared with
When was the document shared
Who processed the document (signer, reviewer, editor, delegator, meeting host, gatekeeper)
When was the document processed
The time taken by the recipient to process the document
Total time taken to process the document
When was the document recalled by the user
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the document package to view its details and click "Signing details" in right panel.
Click "History".
The history will be displayed in right panel.
Activated & Enabled
This status implies that a user's account is activated and their access is enabled in SigningHub. These users can log into their SigningHub accounts and use the system.
Activated & Disabled
This status implies that a user's account is activated but their access has been suspended in SigningHub. These users cannot log into their SigningHub accounts till their access is enabled again by your (enterprise admin).
Enabled
This status implies that a user has been directly registered by enterprise admin with enabled access in SigningHub (by using the "Send Activation Email" option), however the user has not activated their account as yet. These users need to activate their accounts by following the activation email to start using SigningHub.
Activated & Enabled
This status implies that a user's account is activated and their access is enabled in SigningHub. These users can log into their SigningHub accounts and use the system.
Activated & Disabled
This status implies that a user's account is activated but their access has been suspended in SigningHub. These users cannot log into their SigningHub accounts till their access is enabled again by you (i.e. Enterprise Admin).
Enabled
This status implies that a user has been directly registered by enterprise admin with enabled access in SigningHub (by using the "Send Activation Email" option), however the user has not activated their account as yet. These users need to activate their accounts by following the activation email to start using SigningHub.
An Enterprise Administrator with the permissions to manage enterprise users in his role, can import a custom certificate for signing. Furthermore, the signing certificates appear at the time of signing. The signing capacities appear on the signing dialog as per the capacities available in a user's role. Enterprise Roles are described in detail here.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the desired user and click "User preferences" in right panel.
Expand "Add a Signing Certificate" tab and click "Add a Signing Certificate" button.
Provide the Capacity Name , Certificate Alias and Certificate (CER) for your certificate. Enable the "Mark as default" option if you want to display your certificate as selected by default in the signing dialog. Additionally, you can select Level of Assurance and Protect Keys Using Option too. Default selected value for Level of Assurance will be Advanced Electronic Signature and for Protect Keys Using it will be User Password.
Click "Save changes".
Only one capacity can be set as default at a time. If a capacity is already set as default, then setting a new capacity will revoke the previous as the default signing capacity.
Certificate Alias is a Unique Identifier for the signing certificate key and must be the same as provided in ADSS.
The Capacity Name should be unique, user-friendly (consisting of letters and digits) and must not exceed 100 characters.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the desired user and click "User preferences" in right panel.
Under "Add a Signing Certificate" tab, click on the desired certificate and click "Edit" in the right panel.
You can update Capacity Name, Certificate Alias, Certificate (CER) and Level of Assurance for your certificate. Click on the Set as default option if you want to display your certificate as selected by default in the signing dialog.
Click "Save changes" button.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the desired user and click "User preferences" in right panel.
Under "Add a Signing Certificate" tab, click on the desired certificate and click "Remove" in the right panel.
Click "Delete" in the confirmation dialogue.
You can also invite your enterprise users in bulk through a CSV file. The CSV file must have the valid email addresses of the users. SigningHub supports three different types of email headers (i.e. Primary Email, E-mail Address, and Email Address) to pick up the email addresses from a CSV file. This is a smart way for the enterprise admins to invite multiple users to their enterprise account through a single click. The users accepting your invitations are brought into your enterprise as the registered enterprise users. You can search the invitation records on the basis of user's name/ email, and can also sort them in ascending or descending order as required.
A user invitation can have three different statuses:
User Status | Description |
---|---|
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Click "Bulk invite" in "Invitations" section.
Select a role for all the users to be invited. The default role is automatically selected for the invitees, change it as required. The users accepting the invitations will have the same (this) role in the enterprise account.
Select the csv file and click "Submit".
All those users (with valid email addresses in the CSV file) that have not been previously invited, or have declined or have ignored the previous invitation, will be invited. An invitation email and web notification will be sent to each such invitee with the account registration link.
In case registration is disabled at System level ​, invitation can not be send to non-register users.
There are multiple ways to get a CSV file. You can create a CSV file using any word processing, database, spreadsheet or text edit applications. When creating a CSV file, the first row must be the header row that shows the field names for the file. Each subsequent row can then represent a unique user email id along with the user's names (i.e. first name and last name).
A CSV file should contain the following information:
"Email Address" to input user's email id. It is a mandatory column header.
"Last Name" to input user's last name. It is an optional column header.
"First Name" to input user's first name. It is an optional column header.
You can also export your contacts (in a CSV file) directly from Outlook, Thunderbird, or any other email service provider. Since SigningHub is mainly concerned with the email column header of a CSV file, therefore three types of headers are supported, i.e. Primary Email, E-mail Address, and Email Address.
You can edit any content inside a CSV file as required.
In case the contact names are specified in a CSV file (i.e. First Name and/ or Last Name), they will be populated accordingly in the name fields of a contact.
In case a contact name is not specified in any name field, then the contact username (portion of email address before the "@" symbol) will be shown as contact name.
The rest of the column headers inside a CSV file are not related to SigningHub, so they will be ignored when you import the file.
You can export the users invitations to an excel sheet file (xlsx) by clicking "Export to excel" available under "Invitations" section. The excel sheet file is downloaded to your local Downloads folder.
The CSV file being used for inviting the enterprise users in bulk must have the valid email addresses of the users. SigningHub supports three different types of email headers of a CSV file, i.e. Primary Email, E-mail Address, and Email Address. You can export your contacts (in CSV) from Outlook, Thunderbird, or any other email service provider that supports these email headers.
SigningHub provides comprehensive search facility to search your enterprise users. You can either use the default search bar or go for advance search to retrieve an enterprise user from the list. The default search bar allows searching on the basis of user name or their email ID. While if your enterprise users are in bulk and its hard for you to find the required user, you can use combination of multiple parameters to reach the exact user. This input of multiple parameters is called advance searching.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Specify the name or email ID of your enterprise user in the search bar (shows up by clicking "Filter" button).
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Click "Advanced search" button.
Specify the available information in the respective fields and click the "Search" button. SigningHub will retrieve the enterprise user by incorporating all the provided parameters in the search.
​In case of specifying multiple search parameters, the search will be carried out by using AND operator(s) among all the parameters. This helps SigningHub to retrieve more targeted results.
SigningHub enables you to invite users to your enterprise through emails. The users accepting your invitations are brought into your enterprise as the registered enterprise users. You can search the invitation records on the basis of user's name/ email, and can also sort them in ascending or descending order as required.
A user invitation can have three different statuses:
User Status | Description |
---|---|
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Click "Send an invitation" in "Invitations" section.
Specify Name, Email, and Role of the user in the provided fields. The default role is automatically selected for the invitee, change it as required.
Click the "Submit" button. An invitation email and web notification will be sent to the invitee with the account registration link.
In case registration is disabled at System level ​, invitation can not be send to non-register users.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the user you want to resend invite to and click "Resend invite" from right panel. The invitation email will be resent to the user.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the user you want to resend invite to and click "Withdraw invite" from right panel.
Click "Withdraw" from the confirmation dialogue. SigningHub will invalidate the invitation link(s) that have been previously sent to the invited user(s).
You can export the users invitations to an excel sheet file (xlsx) by clicking "Export to excel" available under "Invitations" section. The excel sheet file is downloaded to your local Downloads folder.
The tab lets you configure basic information as well as authentication settings. Basic information consists of role name, description and whether it'll be default for new users or not. The Login Authentication lets you configure a private authentication method in a role. This method is specifically used for the login authentication of your enterprise users, and will not be available to public users under the "More Login Options" link of login screen. At the time of login, SigningHub will check the IDs of your enterprise users and allow them to only authenticate themselves through the private method configured in their role. However they can also login by using "More Login Options" link, if you allow them to use public authentication methods.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Basic Information". Configure the basic information as required.
Click "Save changes".
See the description in the "Basic Information" table below.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Basic Information". Configure the authentication settings as required.
Click "Save changes".
See the description in the "Authentication Preferences" table below.
When you update a role in a production environment, the saved changes are available to the related users on their next login.
​​A private authentication profile is the one that is exclusively used for corporate logins and is not available to the end users (public) on their Login screen and Integration screen of SigningHub Desktop Web.
The availability of private authentication profiles, is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your enterprise service plan. The availability of Time based One Time Password, and One Time Password as a secondary authentication method is subject to your subscribed service plan.
Once the enterprise administrator enforces Time based One Time Password as a secondary authentication method on to a role, and a user under that role does not have two factor authentication (2FA) configured at the time of login, they will be sent an email to set up and to provide a Time based One Time Password. If the user has already configured two factor authentication (2FA) they will be prompted to provide the Time based One Time Password from the authenticator app configured on their mobile device.
To configure the two factor authentication (2FA) the user will need to install an authenticator app (Google Authenticator, Microsoft Authenticator, etc.) on their mobile device. The email sent to the user to configure two factor authentication (2FA) will contain:
QR Code
Manual Key
Recovery Codes
To set up, the user can either scan the "QR Code" or manually input the "Manual Key" in the Authenticator app. Once the registration is successful, the user can provide the automatically generated Time based One Time Password from the Authenticator app to SigningHub in order to proceed. The list of recovery codes included in the configuration email can be used in place of a Time based One Time Password, once each recovery code, to regain access to your SigningHub account, in case you lose access to your mobile device. It is advised to save the recovery codes in a safe place. The user can however, regenerate a new list of the recovery codes from the Manage Two Factor Authentication (2FA) option. In case enterprise user loses access to your mobile device and recovery codes, or have used all of the recovery codes, you can ask your enterprise admin to reset the two factor authentication (2FA) against your account.
The User Access Preferences tab lets you configure the usability related SigningHub modules in a role. You can select your choice modules from the list to make them available to your enterprise users (registered with this role) for navigation. SigningHub supports granular access management along with their fine grained authorization, i.e. read, add/ edit, and delete access on different modules/ sub modules of the system.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "User Access Preferences". Select the user settings check boxes and their respective granular access as required.
Click "Save changes".
See the description in the "User Access Preferences" table below.
When you purchase an enterprise account of SigningHub, a default Enterprise Admin user is provided to you, having all the privileges and access in your SigningHub account. You can use the credentials of your Enterprise Admin to configure the role based granular access (i.e. read, add/ edit, and delete access on different modules/ sub modules of the system) for your enterprise users. You can even create multiple Enterprise Admins as required. When a new Enterprise is created, two roles will also be created in the Enterprise: Enterprise Admins and Enterprise Users. The Enterprise Users role is marked as "default", which means whenever a new user will be created in this Enterprise, the default role will automatically get assigned to the user. However, you can always modify which role should be the default. Remember, only one role can be marked as "default". In addition, you can also add new roles under this Enterprise. Read on to know what more you can do on this page. From here, you can manage (Add, Clone, Edit, and Delete) different roles and can assign them to your enterprise users and external users, in order to provide them custom access in the system. However you cannot delete a role, as long as it is assigned to any user within your enterprise or to external user of third party integration.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Click "Add Role" button.
Add a New Role dialogue will appear. Provide name and description and click "Add role" button to continue.
Fill in all the information in the respective sections.
Click "Save changes" button. Now assign this role to your enterprise user to give them configured access, see Manage your enterprise users.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the desired role and click "Mark Default" button in right panel.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the desired role and click "Clone" button in right panel.
"Clone Role" dialogue will appear. Specify name of the clonal role and its description as required. The clonal role name must be different than the original role name. If you want to make the clonal role as default in your enterprise, tick the "Mark default" check box. SigningHub assigns the default role to those enterprise users, for which Enterprise Admin did not specify any role. The default role is also automatically selected when inviting the enterprise users.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the desired role and click "Edit" button in right panel.
Role screen will appear. Edit the required tabs and click "Save changes".
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the desired role and click "Delete" button in right panel. Please note, you cannot delete a role that is assigned to any user within your enterprise or in third party integration.
Click "Delete" on confirm dialogue.
As a security consideration, always assign least privileges to a default users role. SigningHub assigns the default role to those enterprise users, for which Enterprise Admin did not specify any role. Similarly, the default role is automatically selected when inviting the enterprise users. ​
When you update a role, the saved changes are available to the related enterprise users on their next login.
You cannot downgrade all the Enterprise Admins to Enterprise Users. SigningHub will ensure that at least one Enterprise Admin must be under Enterprise Admin role to manage all the account related configurations.
By default all the enterprise users are registered in SigningHub with the enabled access. However, you can disable your enterprise users when required. The SigningHub access will be suspended with immediate effect for the disabled users, till they are enabled again.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the user you want to disable and click "User preferences" in the right panel.
Switch-off the "Enabled" toggle.
The SigningHub access for this enterprise user will be suspended right away and it will be shown with a strike through line, as shown below:
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Select the disabled user you want to enable and click "User preferences" in the right panel.
Switch-on the "Enabled" toggle. The SigningHub access for this enterprise user will be resumed right away.
​When an enterprise user's access is disabled while they are using SigningHub, they are redirected to the SigningHub Login screen with immediate effect.
When using an on-premises installation, SigningHub gives you an option to pre-authorise users in your Directory so that they may serve as your registered enterprise users. In this way, your enterprise users can use their Directory credentials (i.e. organizational domain user ID and password) for SigningHub authentication, and wont even need to create their SigningHub IDs.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Tick the "Automatically register the users" check box.
The "Authentication Profile" field will appear, listing all the Active Directory Authentication Profiles and the Azure Active Directory Authentication Profiles configured in SigningHub Admin console. Select the required authentication profile from the list.
Click the "Save" button.
All the users that belong to the selected authentication profile will be authorised through Azure Active Directory upon Login, and will be automatically registered and activated in SigningHub under the default SigningHub role, provided that provisioning is not enabled by any other enterprise within the same on-premises deployment.
This implies, if multiple enterprises have been configured within an on-premises deployment, then the "Automatically register the users" check box should be ticked for only one enterprise.
You can also give the role based access of SigningHub (i.e. Enterprise Admin, or Enterprise Users, etc) at Security Group level. SigningHub allows you to manage (Add, Edit, and Delete) the Security Groups from the same screen.
Login with your enterprise admin credentials.
Click "Configurations" from left-menu and click "Users" under "People" options in "Enterprise Configurations" section.
Click "Add a security group".
Specify a Group name.
Now, select a role to assign to this security group and click the "Submit" button. The default role is shown automatically selected for the security group, change it as required.
The added security group will be listed inside the Security Group grid. All the users that belong to the security group will be automatically registered and activated in SigningHub under the specified role.
Select the security group whose role is required to edit.
Click "Edit" in the right panel.
Select the role as required and click "Save changes".
Select the security group required to be deleted.
Click "Delete" from the right panel.
Click "Delete" in the confirmation dialogue.
When using Active Directory authentication for SigningHub Desktop Web, the users to be authenticated should be the part of the same domain where SigningHub has been deployed, e.g. if the users belong to the "Ascertia" domain, then SigningHub should also be deployed on the "Ascertia" domain.
Signature settings are all about configuring the allowed signing methods (i.e., Server-side Signing, Client-side (Local) Signing, and/or Mobile Signing), authentication methods (i.e., No Authentication, OTP via SMS, SigningHub ID, Microsoft Active Directory, Salesforce, Freja eID etc.) and signing capacities in a role. You can separately configure these settings for web browsers and mobile apps, and choose a default signing method for each case. You can also configure Remote Authorized Signing here, which allows a user to authorize a remote signature (done on the server) using their registered mobile device. The device will have its user authentication built-in (touchID or PIN), so in a way they can also configure two-factor authentication. Furthermore, this section lets you manage signing reasons, which are used in the Signature Appearance, and become a permanent part of a PDF signature. The signing reasons can optionally be displayed in the signed PDF document.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Document Preferences" and "Signing Server Preferences" and configure desired setting.
Click "Save changes".
The tab lets you configure which templates and library documents will be accessible by the role.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Template and Library Document Preferences".
In "Allowed Templates" section, enable toggle adjacent to the template you want to allow to be accessible.
You can use "Filter" to search, "Show" drop-down to manage which templates to show and "Disable All" and "Enable All" buttons to manage templates.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Template and Library Document Preferences".
In "Allowed Templates" section, enable toggle adjacent to the template you want to allow to be accessible.
You can use "Filter" to search, "Show" drop-down to manage which templates to show and "Disable All" and "Enable All" buttons to manage templates.
This section also lets you select a signature appearance design, which specifies the user information (i.e., Hand signature with details & company logo, hand signature with details, or hand signature only) to be displayed in a user signature. The configurations set here will be displayed as the default settings to your enterprise users belonging to this role. However, users can overrule these configurations through their personal signature settings or while signing a document.
Additionally you can configure a signature font, when using text based signatures in SigningHub Desktop Web. The signature appearance will be rendered in the same font upon signing.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration.
Search and select the desired role and click on "Edit" button in left panel.
Click "Signature Appearance Preferences".
Click "Save Changes" button.
Signature Pad can be used to perform hand signatures and in-person hand signatures, only on Desktop Web.
Signature Pad can be used to perform initials only on Desktop Web.
​If you clear all the signature appearance designs from the "Allowed Signature Appearance Designs" field, the "Default Signature Appearance" field will also clear up automatically.
If you want to configure a fixed signature appearance design for your enterprise users, belonging to this role, only select one signature appearance design in the "Allowed Signature Appearance Designs" field.
For a new enterprise user, by default, all the signature appearance designs allowed in the user's service plan will be selected in the "Allowed Signature Appearance Designs" field.
For a new enterprise user, by default, the first signature appearance design which was allowed in the user's service plan will appear in the "Default Signature Appearance" field.
For an existing user, if they had previously selected the "All" option to allow all the signature appearance designs, all the signature appearance designs as configured in the user's service plan will now be selected in the "Allowed Signature Appearance Designs" field, by default.
For an existing user, if they had previously selected the "Only" option to allow only one signature appearance design, the same signature appearance design will now be selected in the "Allowed Signature Appearance Designs" field, by default.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration.
Search and select the desired role and click on "Edit" button in left panel.
Expand "Signature Server Preferences" tab and click "Add a Signing Server".
Configure the settings as required.
Click "Done" button.
See below table for description.
When a new signing server is configured in the user role, it will fetch any signature appearance configurations set against the signing server in the service plan, if any.
When a new enterprise user is registered, if a signature appearance was set against this signing server in the service plan, against the user's role, it will be selected as the "Signature Appearance", by default.
Upon changing the selected signature appearance, any uploaded logo will be removed as well.
The "Signature Appearance" field appears for both; server-side signing servers, and local-side signing servers.
Same authentication is applied on Electronic Seal (eSeal), Advanced Electronic Seal (AdESeal) and Qualified Electronic Seal (QESeal) though it will generate different certificates accordingly. Therefore, if you have selected the signing capacities of Electronic Seal (eSeal), Advanced Electronic Seal (AdESeal) and Qualified Electronic Seal (QESeal), then on this screen you will see them bundled as a single authentication.
Signing Servers to be configured under enterprise roles, are subject to your assigned enterprise service plan and only those signing servers will be available under enterprise roles that are configured in your service plan.
When adding a Signing Server for CSC, there is no signing capacities or level of assurance related information appears.
When adding a Signing Server for Client Held Keys using either ADSS or CSC, there will be no further options appears.
The availability of Time based One Time Password, and One Time Password as a secondary authentication method is subject to your subscribed service plan.
Once the enterprise administrator enforces Time based One Time Password as a secondary authentication method for a signing server against a role, and a user under that role does not have two factor authentication (2FA) configured at the time of signing with that signing server, they will be sent an email to set up and to provide a Time based One Time Password. If the user has already configured two factor authentication (2FA) they will be prompted to provide the Time based One Time Password from the authenticator app configured on their mobile device.
To configure the two factor authentication (2FA) the user will need to install an authenticator app (Google Authenticator, Microsoft Authenticator, etc.) on their mobile device. The email sent to the user to configure two factor authentication (2FA) will contain:
QR Code
Manual Key
Recovery Codes
To set up, the user can either scan the "QR Code" or manually input the "Manual Key" in the Authenticator app. Once the registration is successful, the user can provide the automatically generated Time based One Time Password from the Authenticator app to SigningHub in order to proceed. The list of recovery codes included in the configuration email can be used in place of a Time based One Time Password, once each recovery code, to regain access to your SigningHub account, in case you lose access to your mobile device. It is advised to save the recovery codes in a safe place. The user can however, regenerate a new list of the recovery codes from the Manage Two Factor Authentication (2FA) option. In case enterprise user loses access to your mobile device and recovery codes, or have used all of the recovery codes, you can ask your enterprise admin to reset the two factor authentication (2FA) against your account.
When the "Key Protection Option" option is set to 'System Password' (i.e., Sole Control is off) in certification profiles under SigningHub Admin configurations, SigningHub gives you the provision to choose a third-party authentication option for your enterprise users. You may select any of the following 15 options; through which your enterprise users can authenticate themselves for server-side signing.
No Authentication:
Select this option to let your enterprise users sign their documents directly without any authentication. In this case, their server based certificate will be used for signing but system will not prompt for any password or OTP.
SigningHub ID:
Select this option to allow enterprise users to use their SigningHub account password to sign their documents.
Microsoft Active Directory:
Select this option to allow enterprise users to use their Active Directory credentials to sign their documents. SigningHub will require their user ID (as registered in the organisational Active Directory) and domain password for the signing activity. you can authenticate using your Active Directory credentials at the time of signing having a different email address and vice versa.
Microsoft ADFS:
Select this option to allow enterprise users to use their ADFS credentials to sign their documents. SigningHub will require their user ID (as registered in cloud ADFS) and domain password for the signing activity. you can authenticate using your ADFS credentials at the time of signing having a different email address and vice versa.
Microsoft Office 365:
Select this option to allow enterprise users to use their Microsoft Office 365 credentials to sign their documents. SigningHub will require their Office 365 credentials (ID and password) for the signing activity. In case your enterprise user has logged in through SigningHub ID and want to sign through Microsoft Office 365 credentials, then their SigningHub ID (email address) and Office 365 ID (email address) must be the same.
Salesforce:
Select this option to allow enterprise users to use their Salesforce credentials to sign their documents. SigningHub will require their Salesforce credentials (ID and password) for the signing activity. you can authenticate using your Salesforce credentials at the time of signing having a different email address and vice versa.
LinkedIn:
Select this option to allow enterprise users to use their LinkedIn credentials to sign their documents. SigningHub will require their LinkedIn credentials (ID and password) for the signing activity. you can authenticate using your LinkedIn credentials at the time of signing having a different email address and vice versa.
Google:
Select this option to allow enterprise users to use their Google credentials to sign their documents. SigningHub will require their Google credentials (ID and password) for the signing activity. you can authenticate using your Google credentials at the time of signing having a different email address and vice versa.
Freja eID:
Select this option to allow your enterprise users to use their Freja eID authentication to sign their documents. Whenever, your enterprise user attempts to sign a document, a signing request will be sent to their mobile device running the Freja eID app. Upon confirmation from the Freja eID app, the document will be signed.
Authorisation via Mobile App:
Select this option as the Authentication Method to allow your enterprise users to use remote authorised signing provision. This option will only appear for the capacities that has Qualified Electronic Signature (QES) configured as the level of assurance and appears under 'Signing Capacities for Remote Authorization (Owned by User)' category.
OAuth2:
Select this option to allow enterprise users to use your IDP credentials (OAuth2 supported protocol) to sign their documents. SigningHub will require their IDP credentials (ID and password) for the signing activity. you can authenticate using your IDP credentials at the time of signing having a different email address and vice versa.
OIDC:
Select this option to allow enterprise users to use your IDP credentials (OIDC supported protocol) to sign their documents. SigningHub will require their IDP credentials (ID and password) for the signing activity. you can authenticate using your IDP credentials at the time of signing having a different email address and vice versa.
When you update a role in a production environment, the saved changes are applicable to the related users on their next login.
When an In-Progress workflow has reached a stalemate in your enterprise because the next configured recipient is unresponsive, SigningHub gives you authority to either:
Change that recipient and/ or
Send them a reminder
Because of the super admin control, it does not matter whether the "" permissions on the document are allowed or not. In case you select the "Manage Recipient" option, all the for the previous recipient (by their document owner) will be transferred to the new recipient, along with the predefined workflow role (i.e. signer, reviewer, editor, or meeting host).
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the desired document package and click "Manage recipients" in right panel.
A dialog will appear, showing the list of configured recipients in an editable mode. Click edit icon.
A new dialogue will appear. Specify the name(s) or National ID(s) of other recipient(s) that are added in your SigningHub contacts list as required, and the email/mobile number will automatically be updated in the adjacent fields.
Click "Save changes" button.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the desired document package and click "Manage recipients" in right panel.
A dialog will appear, showing the list of configured recipients in an editable mode. Click reminder icon being displayed adjacent to the next configured (first) recipient.
A confirmation dialogue will be displayed, click yes.
You can only change the recipients but not their roles in the workflow. This implies that a signer can be changed with another signer, a reviewer can be changed with another reviewer, and so on.
The pre-configured special privileges (i.e. printing, downloading, adding text, accessing securities like password, OTP, time duration, etc.) as set by the document owner cannot be changed. These settings will be transferred to the new recipient as it is.
SigningHub allows you to keep an eye on all the documents within your enterprise and take appropriate actions against them as required. The documents are listed from document owners' perspective, which implies you can see the workflow progress of documents (i.e. Draft, In-Progress, Pending, Completed, and Declined) that an enterprise user owns.
However to comply with the security and integrity standards, SigningHub wont allow you to open and view any enterprise document that is not related to you.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
All the document packages within your enterprise will be listed in their respective statuses. Click on any document to see further details.
Here is the basic set of information associated with each enterprise document(s) package in the list:
Names of documents separated by commas in a package.
Current status of document(s) package.
Name and email address of document(s) package's owner.
Size of document(s) package.
Date on which document(s) package was last modified, i.e. shared, form filled, signed, declined, etc.
Click "Manage recipients" to access the "Workflow" dialog that displays the workflow information i.e. full list of recipients along with their email address, role, collaboration sequence, and processing status (i.e. done, undone, or declined). In addition, you can also update the placeholders for the recipients.
You can export the metadata related to your enterprise documents in the .xlsx format. The downloaded file will contain the following information about the enterprise documents; Package ID, Title, Owner Name, Owner Email, Date Created, Last Modified, Workflow Type, Status, and the Size. To export the metadata information:
Click on the "Export to excel" button and the .xlsx file containing the metadata of all your enterprise documents will be downloaded.
Click "Advanced search" button. The "Advanced Search" dialog will appear.
Specify the available information in the respective fields and click the "Search" button. SigningHub will retrieve the documents by incorporating all the provided parameters in the search.
In the "Owner" field, a user could enter either the name or the email of the document owner. All the documents containing the searched keyword, as the document owner, will be listed.
In the "Recipient" field, a user could search for a document using either the name or the email of the recipient. All the documents containing the searched keyword, as a recipient, will be listed.
By default all your enterprise document(s) packages are listed in the grid. You can filter them out on the basis of the "Draft", "In-Progress", "Pending", "Completed", and "Declined" statuses.
By default up to 10 document packages are displayed in the main grid. Click next to view more enterprise documents in the list accordingly. The system will keep fetching the ending records accordingly. The system will also show the count of displayed and existing (total) documents at the bottom of the grid.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the desired document package and click "Send the workflow completion report" in right panel.
A confirmation message will be displayed. Click Yes, and the workflow completion report will be published at the Server URL configured in the "Workflow Completion Report" section of the .
SigningHub allows the Enterprise Admin to access the enterprise documents, if you want to view your enterprise documents, go to the enterprise documents.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the document package to view its details and tap on its collapsible name in right panel.
As a matter of super admin control, SigningHub allows you to keep an eye on all the documents within your enterprise and take appropriate actions against them as required. The documents are listed from document owners' perspective, which implies you can see the workflow progress of documents (i.e. Draft, In-Progress, Pending, Completed, and Declined) that an enterprise user owns.
However to comply with the security and integrity standards, SigningHub wont allow you to open and view any enterprise document that is not related to you. You can only take the following actions against your enterprise documents:
The documents screen provides the search and sort facility to easily locate the required documents, and also enables you to filter your enterprise documents list on the basis of up-mentioned statuses.
This status implies that a user's account is activated but their access has been suspended in SigningHub. These users cannot log into their SigningHub accounts till their again by your (enterprise admin).
Select the "Start existing workflow" sub option to show or hide the "" option on the the "Documents Listing" page under the More Options menu.
Select the "Replicate Workflow" sub option to show or hide the "" option on the the documents listing screen under the More Options menu, and on the document viewer screen.
Select a value (i.e., Just Others, Me and Others, or Only Me) from the "Default signing mode" drop-down list that can be set as default when the document owners click the "" button from their System Dashboard or Document Listing screens. They can however change the default workflow mode by clicking the adjacent drop-down list while initiating a workflow as required.
Select a value (i.e. Serial, Parallel, Individual, or Custom) from the "Default signing order" drop-down list which can be displayed (as selected) to the document owners while . They can however change the default workflow type while initiating a workflow as required.
Fields | Description |
---|
Select this option to allow the document owners within your enterprise (belonging to this role) to add signature fields in their workflows. If this option is selected, the "Level of Assurance" and "Default Level of Assurance" mandatory fields will appear for the user to configure. If you keep this option deselected, the document owners will not be able to add the "Signature" field while preparing workflows. The "Level of Assurance" field allows the enterprise admin to configure the levels of assurance that the document owners are allowed to use for a signature field. You can either allow specified levels of assurance or allow all available levels of assurance. The drop down list for this field displays the levels of assurance as configured in the . The possible options for this field are:
For details about the above mentioned levels of assurances, . The "Default Level of Assurance" field defines what levels of assurance will be used by default when the document owners drops a signature field. The system automatically populates this field as per the "Default Levels of Assurance" field, in the service plan. The configured levels of assurance from the "Level of Assurance" field will be listed in the "Default Level of Assurance" drop down list for the enterprise admin to manually configure the "Default Level of Assurance" field. The configuration of this field supersedes the configuration of the "Default Levels of Assurance" field in the service plan. For a new enterprise user under a specific role, the system will pick the configured default level of assurance from this field and set it as the default level of assurance for the user in .
Field | Description |
---|---|
Field | Description |
---|---|
Field | Description |
---|---|
Fields | Description |
---|
Fields | Description |
---|
Fields | Description |
---|
The drop-down list of "Authentication Method" (i.e., SigningHub ID, Salesforce, Microsoft Active Directory, LinkedIn, Google, Bank ID etc.) in server-side signing, depends on the key protection option under your certification profiles. If you are unable to find the required authentication method in the list; contact .
The availability of configuring "OTP via SMS" is subject to your subscribed service plan. If you are unable to find this option in your account; .
"Authorisation via Mobile App" is subject to your signing profile that is configured in your service plan. If there is a signing capacity added for remote authorisation signing under your singing profile then these capacities will appear under signature settings under the label 'Signing Capacities for Remote Authorisation (Owner by User). If you are unable to find this option in your account; contact .
In order to change a recipient of your enterprise document or to send a reminder, ​you must have the "Edit" rights on the "Enterprise Documents" settings, see .
The workflow completion report shall fail to publish if an invalid Server URL has been configured in the "Workflow Completion Report" section of the .
The option to "Send Workflow Completion Report" will be available against an enterprise document, if the "Send workflow completion report" option is enabled in the .
Certify with no changes | Select this option to disallow any changes to the document after the Certified Digital Signature has been applied. The recipients will not be able to add any annotation to the document, fill out PDF forms, or include additional signatures. This option is intended for documents requiring only one signature. |
Certify with form filling and signing | Select this option to allow the recipients to only fill in PDF forms, and sign empty signature fields after the Certified Digital Signature has been applied. They will not be able to add any new annotations to the document. This option is intended for documents requiring one or more signatures. |
Certify with form filling, signing and annotations | Select this option to allow the recipients to fill in PDF forms, sign empty signature fields, and add annotations to the document after the Certified Digital Signature has been applied. This option is intended for documents requiring one or more signatures. |
Role name
Name to be displayed for the role.
Description
Description for the role.
Default
Enable if you want to make it default for new users.
Default Authentication Method
Field to select a private authentication profile for the enterprise users belonging to this role. The drop down will show the list of authentication methods that are allowed in your service plan. When selected, the enterprise user will have to enter their registered ID in the login screen, SigningHub will read their ID and will automatically open the configured (private) authentication method (i.e. SSL authentication, Microsoft Active Directory, Salesforce, Google, etc.) screen for their authentication. Select the "None" option to disable the private authentication for this role. In this case SigningHub will let your enterprise users to use any public authentication from the "More Login Options" link of login screen.
Allow public authentication methods
Tick this check box to allow the enterprise users of this role to either use any public authentication method from the "More Login Options" link of login screen, or use the set private authentication method above to authenticate themselves. In this way they will have the option at the login time, whether to get themselves authenticated via any public authentication method or through the set private authentication method. If you leave this check box unticked against a configured private authentication method, the "More Login Options" link of login screen will be inaccessible to the enterprise users of this role.
Secondary Authentication Method
Field to enforce the enterprise users of this role, to use a secondary authentication method in conjunction with any of the private/ public authentication method. The drop down will show the list of secondary authentication methods that are allowed in your service plan i.e. One Time Password or Time based One Time Password. The enterprise users of this role will have to first provide the correct credentials of private/ public authentication method, and then based on their selected option, provide either:
One Time Password: An OTP will be sent on their mobile devices. The mobile number of an enterprise user on which the OTP is required to send, can be added in their personal profile, see details.
Time based One Time Password: The TOTP from the configured authenticator app on their mobile devices. The two-factor authentication (2FA) can be configured by the user in their personal profile.
Select the "None" option to disable the secondary authentication method for this role.
Signature Settings
Select this option to allow the user signatures configuration access in a role. This will enable the "Signatures" tab under the configurations for your enterprise users belonging to this role.
Groups
Select this option to allow the user groups management access in a role. This will enable the "Groups" and "Contacts" tabs under the configurations for your enterprise users belonging to this role.
Templates management
Select this option to allow the user templates management access in a role. This will enable the "Templates" tab under the configurations for your enterprise users belonging to this role.
Library management
Select this option to allow the user documents library management access in a role. This will enable the "Library" tab under the configurations option for your enterprise users belonging to this role.
Notifications
Select this option to allow the user emails configuration access in a role. This will enable the "Notifications" tab under the configurations option for your enterprise users belonging to this role.
Legal notices
Select this option to allow the user legal notices management access in a role. This will enable the "Legal Notices" tab under the configurations option for your enterprise users belonging to this role.
Delegation
Select this option to allow the delegated signing feature in a role. This will enable the "Delegated Signing" tab under the configurations option for your enterprise users belonging to this role.
Advanced options
Select this option to allow the account deletion feature in a role. This will enable the "Advanced" tab under the configurations option for your enterprise users belonging to this role.
Cloud Drives
Select this option to allow the cloud drive configuration access in a role. This will enable the "Cloud Drives" tab under the configurations option, and the "Get from Cloud" option on Document adding screen, for your enterprise users belonging to this role.
Google Drive: Select this option to allow access to Google Drive in a role.
OneDrive: Select this option to allow access to OneDrive in a role.
Dropbox: Select this option to allow access to Dropbox in a role.
Web Browsers: Types of Hand Signature | The following preferences will be applicable to your enterprise users (that are registered with this role), when they perform signing through Web Browsers:
|
Mobile Apps: Types of Hand Signature | The following preferences will be applicable to your enterprise users (that are registered with this role), when they perform signing through Mobile Apps:
|
Types of Initials | The following preferences will be applicable to your enterprise users (that are registered with this role), when they add their initials:
|
Signature Appearance Designs | The "Allowed Signature Appearance Designs" field allows the enterprise admin to configure the signature appearance designs (i.e., Hand Signatures Only, Hand Signature with Details and Logo, Hand Signature with Details, or any other custom signature design) that the users, belonging to the role being configured, are allowed to use for digital signatures. It is a mandatory field. You can either allow specified signature appearance designs or allow all the available signature appearance designs. The drop down list for this field displays the signature appearance designs as configured in the service plan. The "Default Signature Appearance" field defines what signature appearance design will be used by default when the document owners signs a signature field. Once the enterprise admin configures the "Allowed Signature Appearance Designs" field, the system will automatically populate the "Default Signature Appearance" field. By default, the first allowed signature appearance from the "Allowed Signature Appearance Designs" field will be selected in the "Default Signature Appearance" field. The configured levels of assurance from the "Allowed Signature Appearance Designs" field will be listed in the "Default Signature Appearance" drop down list for the enterprise admin to manually configure it. For a new enterprise user under a specific role, the system will pick the configured default signature appearance from this field and set it as the default signature appearance for the user in Personal Settings.
|
Hand signature font |
|
Allow users to sign documents | Enable this option to allow the users (that are associated with this role) to perform signing operations and signature settings management. If this option is disabled, the below fields will also be disabled:
|
Hide signature dialog at the time of signing | Enable this option to allow the users (who are associated with this role) to skip the signing dialogue box while performing the signature. The signing dialogue box will be hidden if :
|
Allow user to manage contact information | Enable this option to allow the enterprise users (belonging to this role) to view the "Contact Information" field on the signing dialog of signature, and set its value as required before signing. If you keep it deselected, this field will not be shown to the enterprise users on the signing dialogue box. In this case, the default set value will automatically be picked from the user's role upon signing, as highlighted below. |
Allow user to manage location | Enable this option to allow the enterprise users (belonging to this role) to view the "Location" field on the signing dialog of signature, and set its value as required before signing. If you keep it deselected, this field will not be displayed to the enterprise users on the signing dialogue box. In this case, the field value will be selected automatically from the default set value under the user's role settings upon signing. When this option is disabled from roles, then the signing location cannot be updated from the user's personal settings and will be shown as disabled in the user's settings. |
Bulk signing | Enable this option to allow the enterprise users (belonging to this role) to sign and share multiple documents with a single click. They can perform bulk signing from the document listing screen or the document viewer screen. If you keep it deselected, the bulk signing feature will not be available to the users belonging to this role. |
Restrict delegated signing to only registered users | Enable this option to restrict the enterprise users (belonging to this role) to only delegate signing to the registered users. If you keep it deselected, users belonging to this role can choose unregistered users as well for delegated signing. |
Allow user to manage signing reason | Enable this option to allow the users (belonging to this role) to view the "Signing Reason" field in the signing dialog of signature and set its value as required before signing. When 'Allow user to manage signing reason' is selected, there are following three options available further:
|
Manage Signing Reasons | Click the "Add a signing reason" button to add signing reasons. The specified reasons will then be available in the "Predefined" and "Fixed" fields for selection. When used in the Signature Appearance, Signing reason becomes a permanent part of the PDF signature and can optionally be displayed in the signed PDF document. To add a new signing reason, write it in the "Signing Reason" field and click the "Save" button. To delete a signing reason, select the signing reason and click "Delete" button from the right panel. |
SIGNING SERVER |
Keys location | Select the "Keys Location", which display the following options:
|
Signing server | The Signing Server list will display the available signing servers, based on your service plan configurations. You can choose to add a signature appearance to be used for the selected signing server. The "Signature Appearance" list will display the available signature appearances allowed in your service plan. If a signature appearance was set against this signing server in the service plan, it will be selected as the "Signature Appearance", by default. The user can choose to change the default "Signature Appearance" as per their requirements. If the user selects a signature appearance that includes a logo, the "Signature Logo" field will appear, allowing the user to upload a logo. The "Signature Logo" is an optional field. The uploaded logo will be used in the signature appearance when signing with this specific signing server. If a logo has not been uploaded, the system will use the "Signature Logo" configured in the "Branding" section. Only select a "Signature Appearance", if you want the users to use a fixed signature appearance while performing signatures with this specific signing server. If a signature appearance has not been selected, the system will allow the users to perform signing using the signature appearances allowed in the user role. |
Level of Assurance | List of level of assurances available for the selected server at the time of signing.
|
Default signature appearance | Select the default signature, for this server. The user will be able to modify it based on the role settings.
|
Signature Logo |
|
CAPACITIES |
Capacities | This screen lets you configure different "Signing Capacities" for each Level of Assurance. It enables a user to sign on multiple positions within an organisation. When configured, SigningHub creates multiple certificates for the user as per their allowed capacities in the service plan and categorized based on the allowed level of assurances that are configured in the service plan. The user can pick a desired capacity at the signing time and the related certificate will be used in their signature. Add the signing capacities as required for the enterprise user(s) belonging to this role, categorised as per level of assurance. The options available in the drop-down list are allowed in your service plan. If there is only one signing capacity then it will not be displayed in the signing dialog at the time of signing. Only the multiple signing capacities will be displayed in the signing dialog. You can select any one of these available capacities for signing. |
Default Signing Capacity | Select a capacity from the selected ones in this field that will be displayed as the default signing capacity to the user(s) while signing. In a scenario where one or more enterprise users can have the same signing capacities within your enterprise, create a specific role with the desired capacities and simply assign it to them. However, when each user has a different set of signing capacities, then create an exclusive role for each user and configure their signing capacities accordingly. |
AUTHENTICATIONS |
Authentications | This screen lets you select signing-time authentication methods separately for the role. The Levels of Assurance of the selected Signing Capacities are hierarchically grouped under Organization, User and SigningHub Admin. You can select signing-time authentication methods for each of them separately. |
Authentication Method | You can select authentication methods for SigningHub web and mobile apps against the relevant Levels of Assurance. The available authentication methods are subject to your Service Plan configuration. The selected method will be used as authentication method, when your enterprise users sign their documents through any web browser. You can configure both; public and private authentication profiles, under "Authentication Method". See the details of authentication methods below. In case of configuring Remote Authorised Signing (RAS), configure signing capacities for RAS in your Service Plan and "Authorisation via Mobile App" option will appear as Authentication Method for those capacities under 'Signing Capacities for Remote Authorisation (Owned by User). |
Secondary Authentication Method | Select another authentication method (i.e., Time based One Time Password, One Time Password or No Authentication) from the "Secondary Authentication Method" field. This method will be used in addition to the above mentioned authentication method, giving your enterprise users a provision to use a secondary authentication method at signing time. If a secondary authentication for signing through web browsers is not required, then select "No Authentication" from this field. |
Pending
This status implies that the user has not responded to your invitation. The enterprise admin has option to resend or remove the invitation.
Activated
This status implies that the user has accepted your invitation and activated their account. Activated users are the registered enterprise users, and hence they are shown in the "Registered Users" tab only.
Declined
This status implies that the user has rejected your invitation. The enterprise admin has option to resend or remove the invitation.
Pending
This status implies that the user has not responded to your invitation. The enterprise admin has option to resend or remove the invitation.
Activated
This status implies that the user has accepted your invitation and activated their account. Activated users are the registered enterprise users, and hence they are shown in the "Registered Users" tab only.
Declined
This status implies that the user has rejected your invitation. The enterprise admin has option to resend or remove the invitation.
For security reasons, you might need to delete a document package from your enterprise with immediate effect. This includes:
Deletion of the document from owner's account irrespective of its processing status
Deletion of the document from all the recipients' accounts (with whom it has been shared) irrespective of its processing status
Deletion of its workflow and
Deletion of related document logs from the database
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the desired document package and click "Delete" in right panel.
A confirmation message will be displayed. Click Yes. The document will be deleted from your enterprise. A recall notification will be sent to all those recipients who either have processed the document or have the document in their inbox with the "Pending" status.
In order to delete a document from your enterprise, ​you must have the "Delete" rights on the "Enterprise Documents" settings, see details.
If you have standard files that you need to send out over and over again, you can create enterprise templates of those documents, and apply on the same documents (when required) to quickly reuse all the workflow configurations. You can add recipients, form fields, initials, in-persons, signature type, signature position, signing sequence, configure reminders, certify document and much more in an enterprise template. These enterprise templates are available to all the enterprise users within your enterprise, during the document preparation mode, for the efficient and robust re-usability of workflow configurations defined in these templates. From here you can manage (Add, Import, Export, Clone, Edit, and Delete) the enterprise templates as required.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Click "Add template".
Add a document for this template. All the workflow related configurations will be done on this document.
Enable/disable "Read only" as required.
Enable/disable "Public" as required.
Configure certified signature preferences as required.
Add recipient(s) and placeholder(s) as required.
Configure special privileges for each recipient/ placeholder as required.
Click "Continue" to go to viewer screen.
Add data fields for the recipients as required.
Configure form filling settings for a PDF form
Add email message as required.
Once you have set the required configurations, click the "Save and Close" button.
Only those enterprise templates are available to your enterprise users for usage that are marked as "Public". It is therefore recommended not to select the "Public" option, unless an enterprise template is fully configured. Similarly, you can un-select the "Public" option from an existing enterprise template to hide it from your enterprise users.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and its detail will be displayed in the right panel.
At times you need to export the existing templates from your account to your local machine, either to save your account space or share them with others. The templates are exported in json format and can be easily imported later in any SigningHub account. This is the smartest way to reuse or share the same templates without going through any configuration efforts.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and click "Export" in the right panel.
Click "Export" in the dialog appeared. The template will be exported in the json format to your local machine.
You can import the exported templates from one account (source) to another (destination) when required. This is the smartest way to reuse or share the same templates without going through any configuration efforts.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Click "Import".
Drag and drop or select file from you machine in the upload box in right panel and click "Import".
At times you need to create multiple enterprise templates with a little variations. The best way to achieve this is to create a template with all the configurations and then make clones of it. You can then edit each template clone as per requirement.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and click "Clone" in the right panel.
In the dialog appeared, specify name of the clonal template and its description as required. The clonal template name must be different than the original template name. Enable the "Read Only" toggle, if you want to save the clone as a read-only template. Enable/disable the "Public" toggle as required. Only public enterprise templates are available to the enterprise users for usage.
Click "Clone".
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and click "Edit" in the right panel.
Make changes as reqiured and once done, click "Save and close".
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and click "Edit" in the right panel.
From "Documents" screen, specify the name in "Template name".
Click continue to proceed and then click "Save and close".
Login with your enterprise admin credentials.
Click "Configurations" in left menu and select "Templates" under Documents & Signing options in Enterprise Configurations section.
Select any template from the list and click "Delete" in the right panel.
Click "Delete" in the confirm dialog.
You can create as many template clones as allowed in the template quota of your service plan.
The workflow configurations within a read-only template cannot be modified during document preparation, except updating placeholders.
​To experience the exact settings, it is recommended to use the template (being created) on the same documents. The actual positions of configured signature/ initials/ in-person fields may alter, if this template is applied on different type or size of documents.
SigningHub will not allow you to delete an enterprise template if "Any" has been selected under "Allowed Templates" for a user role in the enterprise settings, and the enterprise template being deleted is the only allowed enterprise template for the user role.
Once an enterprise template has been deleted it will be removed from all the user roles under which it was allowed.
The document owner (and the shared folder collaborator, if any) can not update the level of assurance of a "Signature" or an "In-Person Signature" field, while the status of the document is, "In-Progress" or "Pending", where a read-only template has been applied.
If the "Set Document Access Authentication for all recipients" option is selected against the document owner's user role, the document owner will not be allowed to share the workflow until "Document Access Authentication" is set for all the recipient in the workflow.
If the "Set Document Signing Authentication for all recipients" option is selected against the document owner's user role, the document owner will not be allowed to share the workflow until "Document Signing Authentication" is set for all the recipient in the workflow.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
The folders list will appear after documents.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Click "New folder" button.
Enter the name of the folder you want to create and click on the "Save" button. The maximum length of the folder name is 255 characters.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired folder and click "Rename" button in right panel.
Provide the new name and click "Save".
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired folder and click "Delete" button in right panel.
You can not create/rename an enterprise library document folder with the same name as of an existing enterprise library document folder.
You can mark an In-Progress workflow as complete without going through all the recipients. For this, you need to terminate the workflow. This is useful in the cases where a few recipients don't respond to the workflow or the remaining recipients are no more required.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Documents" under Documents & Signing options in Enterprise Configurations section.
Select the desired document package and click "Terminate workflow" in right panel.
A confirmation message will be displayed. Click Yes. The workflow will be terminated and the document package will be marked as "Completed". A recall notification will be sent to all those recipients with whom the document package was shared and they haven't processed it, i.e. the document exits in their inbox with the "Pending" status.
In order to terminate a workflow of your enterprise document, ​you must have the "Edit" rights on the "Enterprise Documents" settings, see details.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Library documents and folders lists will appear.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Click "Add document" button and drag/drop or select the document to upload in right panel.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired document and click "Export" button in right panel.
Click on "Export" in Export Library Documents dialogue. The document along with its configured template (if any) will be exported in the json format to your local machine.
You can import the exported library documents from one account (source) to another (destination) when required. This is the smartest way to reuse or share the same documents along with their configured templates without going through any configuration efforts.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Click "Import" and drag/drop or upload exported document (i.e. .json file).
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired document and click "Export" button in right panel.
Edit the required content i.e. Document name, Template or Folder.
Click "Save".
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired document(s) and click "Delete" button in right panel.
Click "Delete" on confirm dialogue.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Library" in Documents & Signing options in Enterprise Configurations.
Select the desired document(s) and click "Move to folder" button in right panel.
Select the folder and click "Move".
​Each supported document is automatically converted into PDF format, before bringing it to the SigningHub platform.
SigningHub enables you to manage (Add, Edit, Export, Import, Delete, and Move) your frequently used enterprise documents on a centralized location (library) for enterprise-wide utilization. These enterprise documents are available to all the enterprise users within your enterprise, when they add them from SigningHub Library to initiate new workflows. The users can manage their enterprise library documents better by creating enterprise library folders and moving documents between folders.
SigningHub supports accounts multi-tenancy that enables an organisation to define custom signing policies for their external users (i.e. clients, partners, contractors, etc.). The external users are those document recipients who are not a part of your enterprise, they may be a part of other enterprise or individual or guest users, and you require them to sign your enterprise documents within a tightly integrated app environment. In other words, if an Enterprise A requires their documents to be signed by the users of Enterprise B or guest users within an integrated app environment (i.e. Salesforce, SharePoint, MS Dynamics CRM, etc.), then they can assign a default or specific user role to these (external) users, to implement their (Enterprise A) signing policy on such users. With a default user role assigned, all the external users can use a centralized signing policy as laid out in the "Signature Settings" and "Signature Appearance" tabs of the default role. However, in addition to a default role assignment, SigningHub also lets you assign custom user roles to external users on individual basis as required. In this way, when such external users attempt to sign your enterprise documents, SigningHub will supersede the signing policy (defined in the default role or in their enterprise role or their personal) with the ones defined in the user roles you have assigned to them. This is useful when an organization needs to enforce a customized signature policy for certain external users. For more details, visit Ascertia's Partner Portal for Configuration Guide.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Select the desired instance and click "Edit" in the right panel.
Expand "External Users" and click "Add an external user" button from the table. Provide user information in the right panel.
Again, click "Add an external user" button in right panel.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Select the desired instance and click "Edit" in the right panel.
Expand "External Users".
Select the desired user and click "Edit" button in the right panel.
Edit the desired information, in the right panel and click "Update an external user".
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Select the desired instance and click "Edit" in the right panel.
Expand "External Users".
Select the desired user and click "Remove" button in the right panel.
Click "Delete" from the confirmation dialogue.
The external users are those document recipients who are not a part of your enterprise, they may be a part of other enterprise or individual or guest users, and you require them to sign your enterprise documents within a tightly integrated app environment.
The availability of "Integrations" feature is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your service plan.
SigningHub enables you to view the electronic seal related stats of your enterprise. It provides an electronic seal count according to the level of assurance. You can search these records on the basis of "from" and "to" dates and name of electronic seal, sort them in ascending or descending order as required, and can also download them in excel sheet. The "Electronic Seal Statistics" tab will only appear when the "Electronic Seal" feature is enabled in the Service Plan.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Signature reports" under Reports options in Enterprise Configurations section.
Those electronic seals will be listed which have been used to perform signatures according to level of assurance along with their respective counts. Please note the following considerations:
Use the "From" and "To" fields to filter these records on the basis of specified dates.
Use the "Filter" field to filter the records on the basis of electronic seal name.
Click the respective column header to sort the records list in ascending or descending order accordingly.
You can export the document statistics to an excel sheet file (xlsx) by clicking "Export to excel" button. The excel sheet file is downloaded to your local Downloads folder.
​​Please note these stats do not include the signatures which you or your enterprise users have performed for other enterprises. This is because when you sign a document that belongs to another enterprise, the signatures quota of respective document owner/ enterprise is consumed, and hence your signature counts are listed in their account (i.e. Signature reports).
SigningHub enables you to view the signatures related stats of your enterprise. It provides user-based counts of Signatures according to the level of assurance, Simple Electronic Signatures, and In-person signatures of your enterprise documents. This is useful to measure the overall efficiency of users within and outside your enterprise in terms of their signing part, and also helpful to control your billing. You can search these records on the basis of "from" and "to" dates and user name/ email, sort them in ascending or descending order as required, and can also download them in excel sheet.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Signature reports" under Reports options in Enterprise Configurations section.
Expand "Signature Statistics".
Those users will be listed who have performed signatures according to level of assurance, simple electronic signatures, and/ or In-person signatures on your enterprise documents along with their respective counts. Please note the following considerations:
Your enterprise users will be shown with the "Enterprise User" tag below their names.
The users outside your enterprise will be shown without any tag. These are the users with whom you or your enterprise users have shared the documents for collaboration.
Use the "From" and "To" fields to filter these records on the basis of specified dates.
Use the "Filter" field to filter the records on the basis of user name/ email.
Click the respective column header to sort the records list in ascending or descending order accordingly.
The top figures show the accumulated count of each column.
You can export the document statistics to an excel sheet file (xlsx) by clicking "Export to excel" button. The excel sheet file is downloaded to your local Downloads folder.
​​Please note these stats do not include the signatures, simple electronic signatures, or in-person signing counts, which you or your enterprise users have performed for other enterprises. This is because when you sign a document that belongs to another enterprise, the signatures quota of respective document owner/ enterprise is consumed, and hence your signature counts are listed in their account (i.e. Signature reports).
SigningHub enables you to view the graphical representation of signatures related stats of your enterprise. This includes pie-charts, bar charts and timelines of signature activities. Use them to monitor the overall system usage from different aspects to control your billing.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Signature reports" under Reports options in Enterprise Configurations section.
Expand "Signature Charts".
This pie-chart delineates the number of consumed and remaining signatures out of the allotted signature quota of your enterprise account.
This pie-chart delineates the number of consumed and remaining simple electronic signatures out of the allotted signature quota of your enterprise account.
"Simple Electronic Signature Quota" pie chart will only be displayed, if the "SIMPLE_ELECTRONIC_SIGNATURES" module enabled in the license.
"Signatures Quota" pie chart specify digital signatures(PKI signatures) performed using all level of assurance except Simple Electronic Signature (eSignature) if "SIMPLE_ELECTRONIC_SIGNATURES" module enabled in the license.If "SIMPLE_ELECTRONIC_SIGNATURES" module disabled in the license than system will work as of today and specify signatures (PKI or Non-PKI) performed using any level of assurance.
This pie-chart delineates the number of Simple Electronic Signatures (SES), Electronic Seal (eSeal), Advanced Electronic Seal (AdSeal), Qualified Electronic Seal (QESeal), Advanced Electronic Signature (AES) , High Trust Advanced Signature (AATL), Qualified Electronic Signature (QES) and in-person signatures applied out of the consumed signatures quota of your enterprise account.
This pie chart delineates the number of your enterprise users and non enterprise users (i.e. Guest users and External users) who consumed the signature quota of your enterprise account.
This bar chart lets you select a signature level from the given list and specify the date parameters to see its top ten performers from your enterprise users, i.e. Top ten users who have:
Applied the highest number of Simple Electronic Signatures (SES) in a specified time period.
Applied the highest number of Electronic Seal (eSeal) in a specified time period
Applied the highest number of Advanced Electronic Seal (AdSeal) in a specified time period.
Applied the highest number of Qualified Electronic Seal (QESeal) in a specified time period.
Applied the highest number of Advanced Electronic Signature (AES) in a specified time period.
Applied the highest number of High Trust Advanced Signature (AATL) in a specified time period.
Applied the highest number of Qualified Electronic Signature (QES) in a specified time period.
Applied the highest number of in-person signatures in a specified time period.
This timeline lets you choose a signature level from the given list, frequency, and the date parameters to view their respective graph, i.e.:
Total number of Simple Electronic Signatures (SES) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of Electronic Seal (eSeal) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users
Total number of Advanced Electronic Seal (AdSeal) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of Qualified Electronic Seal (QESeal) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of Advanced Electronic Signature (AES) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of High Trust Advanced Signature (AATL) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of Qualified Electronic Signature (QES) applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
Total number of in-person signatures applied on daily/weekly/monthly/yearly basis within a specified time period by all your enterprise users.
SigningHub enables you to manage (Add, Edit, and Delete) enterprise legal notices. These legal notices will be available to all the enterprise users within your enterprise, when they configure recipients in a workflow.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Legal notices" under Documents & Signing options in Enterprise Configurations section.
Click "Add legal notice" button.
Provide "Title", "Content".
Click "Save changes". The saved notices can be used by your enterprise users, while adding them in a template and/ or while adding them in a workflow.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Legal notices" under Documents & Signing options in Enterprise Configurations section.
Select the desired legal notice and click "Edit" in right panel.
Edit the required content and click "Save changes".
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Legal notices" under Documents & Signing options in Enterprise Configurations section.
Select the desired legal notice and click "Delete" in right panel.
Again, click "Delete" in confirmation dialogue.
SigningHub enables you to view the documents related stats of your enterprise. It provides the user based counts of uploaded, shared, signed, approved, updated, and declined documents along with the consumed disk space by them. This is useful to measure the overall efficiency of users within and outside your enterprise in terms of their collaboration part, and also helpful to control your billing. You can search these records on the basis of "from" and "to" dates and user name/ email, sort them in ascending or descending order as required, and can also download them in excel sheet.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Document reports" under Reports options in Enterprise Configurations section.
Expand "Document Statistics".
Those users will be listed who have uploaded, shared, signed, declined, approved, and/ or updated the documents for your enterprise along with their respective counts. Please note the following considerations:
Your enterprise users will be shown with the "Enterprise User" tag below their names.
The users outside your enterprise will be shown without any tag. These are the users with whom you or your enterprise users have shared the documents for collaboration.
Use the "From" and "To" fields to filter these records on the basis of specified dates.
Use the "Filter" field to filter the records on the basis of user name/ email.
Click the respective column header to sort the records list in ascending or descending order accordingly.
The top figures show the accumulated count of each column.
You can export the document statistics to an excel sheet file (xlsx) by clicking "Export to excel" button. The excel sheet file is downloaded to your local Downloads folder.
These stats do not include the signing, approving, updating, or declining counts of those documents, which you or your enterprise users have done for other enterprises. This is because when you sign a document that belongs to another enterprise, the signatures quota of respective document owner/ enterprise is consumed, and hence your collaboration part (counts) is listed in their account (i.e. Document reports).
SigningHub enables you to view the graphical representation of documents related stats of your enterprise. This includes pie chart, bar chart and timeline of document activities. Use them to monitor the overall system usage from different aspects to control your billing.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Document reports" under Reports options in Enterprise Configurations section.
Expand "Document Charts".
This pie chart delineates the status based counts of documents within your enterprise account, i.e. Draft, In Progress, Pending, Signed, Approved, Updated, Declined, and Completed documents.
You can click on any to exclude from the graph.
This bar chart lets you choose a document activity from the given list and specify the date parameters to see its top ten performers from your enterprise users, i.e. Top ten users who have:
Shared the highest number of documents in a specified time period.
Uploaded the highest number of documents in a specified time period.
Signed the highest number of documents in a specified time period.
Declined the highest number of documents in a specified time period.
Approved the highest number of documents in a specified time period.
Updated the highest number of documents in a specified time period.
Consumed the most portion of disk space in a specified time period.
This timeline lets you choose a document activity from the given list, frequency, and the date parameters to view their respective graph, i.e.
Total number of documents shared on daily basis within a specified time period by all your enterprise users.
Total number of documents signed on weekly basis within a specified time period by all your enterprise users, and so on.
SigningHub enables you to customize the color scheming of your SigningHub enterprise account according to your company brand. There are 13 levels of customization that could help an enterprise admin to tune each and every bit (i.e. company logo, Headings, top bar background, buttons background, toaster background, Email headers, etc.) of their SigningHub account in order to make it look exactly the same like their own enterprise brand. Once you are done with branding your enterprise account, share your with your enterprise users so that they may see the branded enterprise interface right from the login screen. You can even customize the error messages content (i.e. images and text), see .
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Branding" in Settings options in Enterprise Configurations.
Expand the "Logos" tab. Browse the images for your Company Logo, Signature Logo and Favicon as required. From here:
The set Website logo will be shown on the login page and on the left side of the top bar.
The set Signature Logo will appear on signature appearance if the user is allowed to manage logo under roles.
The set Email Logo will appear in all enterprise and personal email notifications.
The set favicon will be displayed in the title of your browser tab.
Expand the "Colour Palette" tab, and customize the colour schemes of required areas. You can also use hex colouring codes to specify your choice colour.
Click the "Save changes" button to apply these changes. In case you want to revert the changes to their default, click the "Reset to default" button.
SigningHub enables you to manage (Add, Edit, and Delete) the Electronic Seals of the enterprise. These enterprise Electronic Seals are available to the enterprise users within your enterprise, based on their role, when they need to add an electronic seal to a workflow. The "Electronic Seals" section will appear if "Electronic Seals" is enabled, as a featured, in the service plan.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Electronic seals" in Documents & Signing options in Enterprise Configurations.
Electronic seals list will appear.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Electronic seals" in Documents & Signing options in Enterprise Configurations.
Click on "Add electronic seal" button.
Provide the required information and click "Save changes".
The following table describes the fields on the "Basic Information" section of this dialog.
The following table describes the fields on the "Appearance" section of this dialog.
The following table describes the fields on the "Details" section of this dialog.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Electronic seals" in Documents & Signing options in Enterprise Configurations.
Select the desired electronic seal and click "Edit" in right panel.
Edit the required information and click "Save changes".
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Electronic seals" in Documents & Signing options in Enterprise Configurations.
Select the desired electronic seal and click "Delete" in right panel.
Click "Delete" on confirm dialogue.
The electronic seal feature works with all CSC-based TSPs that support the OAuth 2.0 Client Credentials flow (authType=oauth2client), and credentials having Explicit authMode protection via only a PIN.
The primary colour setting allows you to define a colour scheme that reflects your brand identity across various UI elements, including web and email templates. This primary colour is applied to elements such as buttons, toggles, and action prompts, helping users recognize your brand consistently. Accessibility is a key consideration here; the primary colour should contrast well against the background to ensure readability without the need for additional background elements. We recommend testing the primary colour on both light and dark backgrounds to confirm it meets accessibility standards and enhances user experience.
SigningHub allows you to view Advanced Reports based on the allowed enterprise's data. These reports are fetched from the Microsoft Power BI App as created in the Microsoft Azure Active Directory. This tab will be displayed if you are the Enterprise Owner or its child user and, the "Advanced Enterprise Reports" configuration, is allowed against your .
Login with your enterprise admin credentials.
Click "Configuration" in left-menu.
Click "Advanced Reports" under "Reports" options in "Enterprise Configurations" section.
To view a report, select an available report from the "Report" drop down, and click on the "Load Report" button.
SigningHub allows digital signatures to be easily integrated into any website/app through simple API calls. This is the smart way of adding Advanced Electronic Signatures into a web application that ensures a seamless experience for the end users. SigningHub also facilitates multi-tenancy that enables an organisation to define custom signing policies for their external users (i.e. clients, partners, contractors, etc.). The external users are those recipients who are not a part of your enterprise. They would be either part of another enterprise, an individual user, or a guest (non-SigningHub registered user), and you require them to sign documents within a tightly integrated app environment. This feature is usually requested by the banks and financial institutions, who appreciate high-trust digital signing with tailor-made configurations to ensure a consistent signature style (appearance, details, etc.) for all users. For more details, visit for Configuration Guide. You can integrate multiple web applications with your enterprise account. For details, see the Quick Integration guide and visit for API Guide. With respect to security, and embedded iframes used by SigningHub for tight integration, the Integrations set-up allows you to specify the trusted domains of your business application. When you supply input variables under "Allowed Domains" SigningHub will create the appropriate Internet headers when the iframe is called by the business application. These are X-Frame-Options ALLOW-FROM for older browsers and CSP: frame-ancestors Header for the latest versions of Chrome for example. If you do not specify a value it will allow all parent domains to add this integration page in an iFrame.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Click "Add an Integration" button.
Configure the required information.
Click "Save changes".
In case the specified URL is invalid or inaccessible, SigningHub will send an email to the document owner upon workflow completion.
If the document package contains a single document, its document type will be PDF in the workflow completion report (XML).
If the document package contains multiple documents, their document type will be ZIP in the workflow completion report (XML).
If both, the "Add the completed document" and the "Add the workflow evidence report (WER) in the report" have been enabled, their document type will be ZIP in the workflow completion report (XML).
The "Add the workflow evidence report (WER)" will only appear if the "Detailed with Workflow Evidence Report" option has been enabled against "Workflow Evidence Recording" in the user's service plan.
If only the "Add workflow evidence report (WER)" is enabled, its document type will be PDF in the workflow completion report (XML).
If both, the "Add the completed document" and the "Add the workflow evidence report (WER)" have been enabled, their document type will be ZIP in the workflow completion report (XML).
The system will only send the webhooks and the workflow completion report, if both the document owner and the recipient belong to the same enterprise.
The publishing behavior of the system with respect to whether the webhooks and the workflow completion report have been configured in the document owner's enterprise settings, and in the integration settings of the recipient's enterprise, is as below:
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Select the desired instance and click "Edit" in the right panel.
Configure the required changes in the relevant section.
Click "Save changes".
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Integrations" in Settings options in Enterprise Configurations.
Select the desired instance and click "Remove" in the right panel.
Click "Delete" in the confirmation dialogue.
In order to use the Single sign-on (SSO) facility in SigningHub, the "Default Authentication Method" must either be Microsoft Active Directory, Microsoft ADFS, SalesForce, or Microsoft Office 365.
The external users are those document recipients who are not a part of your enterprise. They would either be part of another enterprise, an individual user, or guest non-SigningHub registered users, and you require them to sign documents within a tightly integrated app environment.
The availability of "Integrations" feature is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your service plan.
ClientID cannot be set as 'MobileSDK' or 'MSOfficeApp', since it has been preoccupied by the SigningHub application for it's Mobile version and MS Office App.
The error colour settings provide options to set the colour scheme for error notifications, ensuring users quickly recognize issues. This section enables you to choose a distinctive colour, typically red, for error alerts, buttons, and messages, making it easy for users to identify critical errors. Accessibility recommendations suggest selecting a shade that provides strong contrast against the background, so error messages remain prominent. This helps maintain consistency across the application, allowing users to identify and address issues efficiently without confusion.
The sidebar navigation settings allow you to customize the background and text colours of the main sidebar, which serves as the primary navigation area within the application. This section includes options to adjust colour schemes for icons and labels within the sidebar, supporting both functional clarity and brand consistency. The contrast of text and icons against the sidebar background is crucial for readability, particularly in low-vision settings. This configuration helps users easily navigate to key areas like the Dashboard, Documents, and Configurations with enhanced visual clarity.
SigningHub allows two types of integration with third party applications, i.e. and . If the "Integration" role is enabled in your subscribed service plan, you can integrate SigningHub with your business application using the REST architectural style APIs. For details, see the Quick Integration guide.
This section covers the following details:
SigningHub lets an enterprise admin configure enterprise account settings. In this regard, the enterprise admin can manage enterprise profiles, registered users, enterprise contacts, enterprise groups, enterprise roles, enterprise templates, enterprise documents library, enterprise email notifications, enterprise branding, third-party integrations and advanced settings.
Fields | Description |
---|---|
Fields | Description |
---|
Fields | Description |
---|
Fields | Description |
---|
Fields | Description |
---|
Fields | Description |
---|
This option will only redirect users to the call-back URL, automatically, if the "Automatically proceed with workflow upon completion of mandatory actions by signer" is enabled, under "".
Fields | Description |
---|
Irrespective of the or the , the document processing report (XML) will only be sent if the "Send the document processing report (XML)" option is allowed, in . By default, the "Send the document processing report (XML)" option will be allowed for all new workflows.
Fields | Description |
---|
Field to specify email id of an external user to whom you want to assign a custom user role within this integrated app.
Role
Select an appropriate role for this external user. When the specified external user will attempt to sign your enterprise documents through this integrated app, SigningHub will supersede the signing policy of the default role with the one defined in this user role.
The user roles can be managed from Enterprise Configurations > People > Roles.
Name | Specify a unique name for this electronic seal, i.e. Peter Kavin-Electronic Seal. |
Role | Select a role from the existing enterprise roles. The users of the selected role will be able to use this electronic seal. |
Signing Server | This field will display the Electronic Seal Signing Servers configured in the service plan. Signing Capacity The "Signing Capacity" field appears only when an ADSS Electronic Seal Signing Server is selected. From the drop down, select a signing capacity for this electronic seal. Credential ID and Credential PIN The "Credential ID" and "Credential PIN" fields appear only when a CSC Electronic Seal Signing Server is selected. Specify a Credential ID and a Credential PIN for this Electronic Seal. |
Level of Assurance | When an ADSS Electronic Seal Signing Server is selected, the "Level of Assurance" field will be disabled. The "Level of Assurance" field will display the level of assurance associated with the above configured "Signing Capacity". When a CSC Electronic Seal Signing Server is selected, from the "Level of Assurance" drop down select the level of assurance which you want your electronic seal to feature. |
Appearance Design | This field is used to configure the signature appearance design (i.e., Hand Signatures Only, Hand Signature with Details and Logo, Hand Signature with Details or a Custom Appearance) for your signature. The available appearances are as per the configuration in the service plan. Choose your appearance from the available ones. In case of selecting an appearance that includes "Logo", a logo field with a "Browse" button will appear to input your company logo image that will be used in your signature appearance. You can then crop this image to remove unnecessary white spaces as required. |
Hand Signature | This field is used to upload a hand signature image to be included in the signature appearance. You can then crop this image to remove unnecessary white spaces as required. |
Signed By | Specify the name which will appear against the "Signed By" attribute to be included in the signature. |
Signing Reason | Specify the signing reason which will appear against the "Reason" attribute to be included in the signature. |
Location | Specify the location which will appear against the "Location" attribute to be included in "Signature Verification Details" dialog. This is an optional field. |
Contact Information | Specify the contact information which will appear against the "Contact Info" attribute to be included in "Signature Verification Details" dialog. This is an optional field. |
Webhooks | Specify a callback URL where SigningHub could send the HTTP POST update of each workflow of the integrated application. This is useful in those cases where all the configured recipients don't necessarily need to process a document package to complete their workflow. The workflow completion can be controlled by an external business application that could decide on need basis, whether to mark a document as complete or not after every major processing activity performed on it. When a URL is provided, this POST request provides the information of each workflow like:
Enable the below for when you want the system to send a document processing report (XML) of the integrated application to the provided server address.
The business application can then use the respective SigningHub API call to inform SigningHub that a workflow is complete and hence no need to send this document to the remaining recipients. Also while marking a workflow as complete, if any recipient of it has got this document in the "Pending" state, then SigningHub will delete the document from their inbox. |
Workflow Completion | This area allows you to configure report routing of the integrated application upon workflow completion. Send the workflow completion report Enable to automatically post the workflow reports of the integrated application (in XML format) to the configured address when the workflow completes. This applies to all users within your integrated application. When enabled, the "Server URL" and "Add the completed document" fields are displayed. Server URL Enable to specify the web server URL where the workflow completion reports of the integrated application are required to send. SigningHub gives you an option to publish Workflow Completion Reports along with the completed documents to a specific web server/URL. This configuration is at the integration level. The metadata and signed documents allow third party business applications to closely integrate with SigningHub and prevent the need to poll to check for complete status. For further details refer to "Publish Workflow Completion Report". Add the completed document Enable "Add the completed document" to receive the completed document along with the workflow completion report. Add the workflow evidence report (WER) Enable "Add the workflow evidence report (WER)" to receive the workflow evidence report along with the workflow completion report; else, leave empty. |
Webhooks and the Workflow Completion Report are configured in the document owner's enterprise settings | Webhooks and the Workflow Completion Report are configured in the integration settings of the recipient's enterprise | System Behavior Publishing Webhooks and the Workflow Completion Report |
Configured | Configured |
|
Configured | Not Configured |
|
Not Configured | Configured |
|
Not Configured | Not Configured |
|
SigningHub lets you configure the advance settings of your enterprise account. From here, you can configure default document and recipients permissions, role for unregistered users, account storage, password policy, legal notices, and certificate filters of your enterprise account, by using your admin credentials.
This section covers the following details:
Client ID | Field to specify the client ID (application name) to be integrated, i.e. SalesforseApp. |
Call-back URL |
Default Role For External Users | This field is related to multi-tenancy functionality, see visit Ascertia's Partner Portal for Configuration Guide. Select a default role for all those users who don't belong to this enterprise, to make them use your custom signature settings. |
Allowed Roles For Scope | This field is available if you want to define SigningHub roles, to restrict a Business Application from performing actions on behalf of users, that are members of these roles. Clicking on this field will display a drop down containing all the configured roles of the enterprise. Select the pre-defined roles that you want to allow, multiple roles can be selected. Leaving this filed blank will be considered as if no restriction has been applied i.e. The Business Application can perform actions on behalf of all the users of an enterprise. |
Application Permissions for Scope | This field is available if you want to define a SigningHub role with specific permissions, enabling Business Applications to perform only the allowed actions on behalf of enterprise users. Clicking on this field will display a drop down containing all the configured roles of the enterprise. Select the pre-defined role that you want to allow for performing actions. Only a single role can be selected, at a time. Leaving this filed blank will be considered as if no role has been specified i.e. The Business Application can perform all actions on behalf of the enterprise users. |
Hide Documents From Recipients | This field is related to multi-tenancy functionality and is used to hide your shared documents from the external users, visit Ascertia's Partner Portal for Configuration Guide. You can select any of the three options, i.e.:
|
Allowed domains, separated by commas | Specify the domain(s) that are allowed to embed the Document Viewer within the iframe. Only the specified domains would be able to embed the Document Viewer within the iframe. Leaving this filed blank will allow all the domains to embed the Document Viewer. |
Collapse the document viewer's recipient and document panels by default. | Check this checkbox to open the Document Viewer inside the tight integration screen with collapsed left and right (i.e. Documents and Recipients) panels. However, users can still open these panels by clicking their respective icons. Keep this checkbox unchecked if there is no such requirement. The Document Viewer will open with the left and right panels intact. |
Automatically redirect to the callback URL after task completion. | Check this checkbox to automatically redirect a user to the call-back URL after they have performed signatures or In-person signatures. By default, this checkbox will be unchecked. Keep this checkbox unchecked if you do not want to have a user automatically redirected to the call-back URL. After the user has performed their task, they will stay on the document viewer screen and will not be redirected unless they press the "Close" button. |
It is generally recommended to downgrade your account to a free version instead of deleting it. In this way you can retain access to your important documents, however you will not be able to share them further for approval purpose. If you are still looking to remove your enterprise account from SigningHub, then you will have to manually delete all your enterprise users first. System not allow you to delete the account if any enterprise user exists in it, except the enterprise owner.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Advanced Settings" under Settings options in Enterprise Configurations section.
Tap on the Account Deletion and click "DELETE ENTERPRISE ACCOUNT" button.
Click "Send deletion email" button on "Delete my account" dialogue. A confirmation email will be sent to you with an encrypted link of account deletion. Click "Delete Account" from the email to conclude the enterprise account deletion process.
Make sure you have deleted all the enterprise users from your enterprise account before clicking the ​"Delete Enterprise Account" button. SigningHub will not allow you to delete the account if any enterprise user exists in it, except the enterprise owner.
"Privacy Policy" related information will not appear while deleting an account, if no Service Agreement is marked active.
SigningHub allows you to configure default settings for your enterprise account. This enables your enterprise users to perform their tasks more efficiently and faster. In particular, it reduces the number of API calls required for standard workflows to increase the speed of integration with third-party business applications.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Advanced Settings" under Settings options in Enterprise Configurations section.
Tap on the Default Settings tab, configure the desired settings and click "Save changes".
There are different types of settings that you may configure:
Login Based Settings
Document Settings
Recipient, Document, and Reminder Permissions
Default Role for Unregistered Users
Witness Signature Reason
Password Strength Policy
Optimize Storage Space
Alert Setting
There are two configurations, i.e.:
Auto trigger authentication profile
Automatic location detection
The "Auto trigger authentication profile" option will only appear when your subscribed Service Plan allows the use of a private authentication. To automatically trigger a private authentication profile for your enterprise users, select this option and choose an authentication profile from the list. The list will display all the private authentication profiles that are allowed in your Service Plan. Enterprise users browse to your configured enterprise URL for login, and configured authentication profile is automatically triggered without the need for the user to identify themselves first. This means they do not have to submit their respective email address in order to start the authentication process. The "Automatic location detection" option allows SigningHub to auto detect the country of your enterprise users when they login from a different location (other than what is configured in their profile) and show it in a pop up. The users will then have the option whether to update the location information in their profile or not. Keep this option un-selected if you don't want SigningHub to detect the location of your Enterprise Users.
Set the default document settings for a new workflow:
Enable this to add a unique identifier field by default in the PDF documents header on Upload. A unique identifier will remain the same for all the documents in a single document package of a workflow.
The Enterprise Users can however overrule these default settings as required while configuring their workflows.
​This section will be visible when your subscribed Service Plan enables the option of "Add a unique identifier in the document header on uploading a document" in its Documents tab.
Set the default recipient, document, and reminder permissions for a new workflow:
The Enterprise Users can however overrule these default settings as required while configuring their workflows.
This section only defines the default recipient, document, and reminder permissions for a workflow. The enterprise users can overrule these default settings as required while configuring their workflows.
The reminders shall be sent based on the configuration of the "Send Reminder Notification Time" thread in the core settings in SigningHub Admin.
Role that will be used for guest/unregistered users when they sign a document. The user roles are managed from the Roles section, see details.
A guest user can apply a digital signature to a document if "No Authentication" is set in the assigned role. They would need to register to perform this action. A guest user can also choose language from the Document Viewer screen, if they are directly signing a document from an email link. However, this feature is controllable from SigningHub Admin.
This options shall only appear if a GeoIP connector has been configured in the SigningHub Admin's "Global Settings" page. The "Auto detect location and timezone for unregistered users" feature allows SigningHub to automatically detect the location and time zone of a guest user. ​By default, this option will be disabled.
In the following situations, SigningHub will use the location and time zone configured under "Global Settings" in the SigningHub Admin, for all the unregistered users:
If the GeoIP connector has not been configured in the SigningHub Admin.
If the GeoIP connector has been configured but is either faulty or not functional.
If the GeoIP connector is functional but the "Auto detect location and timezone for unregistered users" option is disabled.
Reason that will be used by your enterprise users when they add a witness digital signature on a document. With this you can make the witness signing reason uniform across your enterprise. Use the [USER_NAME] variable in the field if you want to include the names of enterprise users (in the reason) before adding witness digital signatures. It will be auto filled-in by SigningHub with respect to each user while signing.
A witness digital signature is a digital signature that is generated by using a public signing certificate (also known as witness certificate) available on the server.
Configure the enterprise password policy for your enterprise users. The enterprise users will have to comply with the configured policy upon set/reset of their account passwords. Configure the password restrictions as required by ticking the relevant check boxes:
Minimum Characters in Password
Include at least one upper case character
Include at least one numeric character
Include at least one special character
Enforce a password change upon next login - Enable this to enforce your Enterprise users to change their password after first login. This will be applicable to the newly registered users only.
Set a password expiration duration - Enable this to auto-expire the passwords of your enterprise users after a certain time period. Specify the number of days in the "Expiry Duration (Days)" field after which SigningHub should expire the user passwords.
Based on your subscribed Service Plan, SigningHub assigns a specific storage quota to your enterprise account. This can be increased by contacting Ascertia Support if required. The storage space can be seen by viewing your current Enterprise Service Plan. It is recommended to effectively utilize the account storage space by keeping document revisions and final signed documents on your local system, cloud drives, or document management system.
Enable "Save every document revision":
When enable, the system will start maintaining the downloadable document revisions for each change in the document (i.e. new sign, adding text, filling initials, etc.) along with their logs. These document versions provide complete document tracking, but consume more storage. The enterprise users within your enterprise will be able to download all these document revisions, by using the "Workflow history" option.
When disable, the system will stop maintaining the downloadable document revisions for each change in the document (i.e. new sign, adding text, filling initials, etc.). The enterprise users within your enterprise will be able to download only the initial and final versions of the document, by using the Workflow history option. However, the log of each change in the document is maintained accordingly.
Specify the time in seconds after which the system notifications should disappear. The displayed value is the one that is configured in SigningHub Admin. You can change this time for your Enterprise account as required.
A private authentication profile is the one that is exclusively used for corporate logins and is not available to the end users (public) on their Login screen and Integration screen of SigningHub Desktop Web. The availability of private authentication profiles is subject to your subscribed Service Plan. If you cannot find this option in your account, upgrade your enterprise service plan.
If the enterprise users within your enterprise are bothered to authenticate themselves for every new signing request, SigningHub gives you document accessibility preferences to skip the authentication step for them. In this way, a recipient (enterprise user) wont need to log into their SigningHub account to access a shared document for processing. This setting will only work when they use email links (i.e. the document links sent to them in the notification emails) or integrated apps. However, the other document accessibility permissions (i.e. Document access via password, Document access via OTP, and/ or Document access duration) will remain effective for the recipients as per the document owner's configurations, and hence cannot be overruled by this setting. Moreover, the user can specify a URL of any web page where you want to redirect the recipients (coming via email link) upon finishing their signing activity. User may show anything on this web page as it is managed and hosted by your organisation. Similarly, user can also specify a callback URL to allow your business application to control the completion of document workflows by using WebHook.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Advanced Settings" under Settings options in Enterprise Configurations section.
Expand "Additional Settings" tab.
Specify the access permission for recipients using email link to access documents, Redirect URL on Close / Finish and Webhooks, and then scroll the page to view more options.
Specify the Work Completion section as needed.
Click "Save changes".
​The images used here contains example data populated in the fields. By default, the fields on the application do not contain any pre-populated information.
The following table illustrates the fields on the Accessibility Preferences:
In case the document owner has configured the other document accessibility permissions (i.e. Document access via password, Document access via OTP, and/ or Document access duration), the user must authenticate themselves accordingly to access the shared document.
Irrespective of the enterprise settings or the integration settings, the document processing report (XML) will only be sent if the "Send the document processing report (XML)" option is allowed, in post processing. By default, the "Send the document processing report (XML)" option will be allowed for all new workflows.
In case the recipient is an individual user or belongs to another Enterprise, the "Workflow Completion" settings of the Document Owner's Enterprise will rule.
The availability of "Workflow completion report" feature is subject to your subscribed service plan. If you cannot find this option in your account, upgrade your service plan.
In case the specified URL is invalid or inaccessible, SigningHub will send an email to the enterprise admin upon workflow completion.
If the document package contains a single document, its document type will be PDF in the workflow completion report (XML).
If the document package contains multiple documents, their document type will be ZIP in the workflow completion report (XML).
If both, the "Add the completed document" and the "Add the workflow evidence report (WER)" options have enabled, their document type will be ZIP in the workflow completion report (XML).
The "Add the workflow evidence report (WER)" option will only appear if the "Detailed with Workflow Evidence Report" option has been selected against "Workflow Evidence Recording" in the user's service plan.
If only the "Add the workflow evidence report (WER)" is enabled, its document type will be PDF in the workflow completion report (XML).
If both, the "Add the completed document" and the "Add the workflow evidence report (WER)" options have been enabled, their document type will be ZIP in the workflow completion report (XML).
The publishing behavior of the system with respect to whether the webhooks and the workflow completion report have been configured in the document owner's enterprise settings, and in the integration settings of the recipient's enterprise, is as below:
The XML of document processing report is composed of a header and all the workflow related actions that have been performed on the document, i.e. Shared, Signed, Reviewed, Edited, Carbon Copied, Recalled, Declined, Completed, and Deleted. A sample XML that is published on server is shown below:
The XML of workflow completion report is composed of a header and all the actions that have been performed on the document, i.e. Opened, Closed, Signed, Reviewed, Declined, etc. A sample XML that is published on server is explained below:
The yellow highlighted portion depicts the XML header, which displays the "Package ID", "Document ID", "Document Name", "Documents", "Document Type", and "Document" information. However, the "Document" tag is optional and displays the base 64 encoded bytes of the document.
The red highlighted portion depicts all the performed actions on the document that have been logged in the form of action tags. You can expand any action tag to view its associated details. For example, the highlighted action shows the "Date Time" on which action was performed, the "Type" of action, the "User ID" who performed the action, the "Enterprise Name" to whom user belongs, the "Information Type & Value" through which (medium) document was accessed. For more details regarding logged actions see Workflow history.
In workflow completion report, both the <DocumentID> and the <PackageID> tags, contain the information of the Package ID.
In case of multiple documents within a package, the <Id> tag will contain the individual document ID, and the corresponding <Name> tag will contain the individual document name.
SigningHub allows you to enable/ disable On-Screen, Email/SMS and Push notifications for your enterprise. These notifications are specifically associated with their accounts and workflow related activities, and are used to intimate them and their recipients when any immediate attention is required. The configured settings from here will be applicable to all the enterprise users' accounts within your enterprise.
The "On Screen" notifications are those that usually appear under user's system notifications for account related events.
The "Email/SMS" notifications are those that are sent through emails to enterprise users and their recipients for any workflow related actions.
While the "Push" notifications are sent on those users' mobile devices (as a pop-up message) on which SigningHub Mobile app (i.e. Android or iOS) has been installed. Users don't necessarily have to be in the SigningHub Mobile app or using their devices to receive them.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Notifications" in Settings options in Enterprise Configurations.
Under the "Notifications" tab, switch on the relevant buttons toggles (i.e. On Screen, Email/SMS, and/ or Push) as required to configure the notification(s) accordingly for your enterprise users. You can also tick all the check boxes against an event.
Click "Save changes" button.
"Simple Electronic Signature LImit Reached" option will only be displayed, if the "SIMPLE_ELECTRONIC_SIGNATURES" module enabled in the license.
Signatures specify digital signatures (PKI signatures) performed using all level of assurance except Simple Electronic Signature (eSignature) if "SIMPLE_ELECTRONIC_SIGNATURES" module enabled in the license. If "SIMPLE_ELECTRONIC_SIGNATURES" module disabled in the license than system will work as of today and specify signatures (PKI or Non-PKI) performed using any level of assurance.
By default, On screen and Email/SMS notifications are sent to pending recipients only.
The enterprise users within your enterprise can overrule these enterprise notifications configurations through their personal notifications settings.
The emails sent from an enterprise account and from SigningHub to the enterprise users are branded as per the enterprise branding configurations, and will have the company defined customisations (i.e. header, footer, logo, etc.) in the email content.
In case constraints are set to unlimited in Service Plan for Templates, Workflows, Users and Signatures then Limit Reached Notifications will be hidden for the account owner.
The SMS notifications will only be sent, if the "Enable SMS notifications" option is enabled in your service plan.
SigningHub enables you to even customize the content of email notifications that are associated with the workflow activities. These emails are used to intimate the enterprise users, Document Owner and recipients about their account related events and workflows progress. The configured settings from here will be applicable to all the enterprise users' accounts within your enterprise.
Login with your enterprise admin credentials.
Click "Configuration" in left menu and click on "Notifications" in Settings options in Enterprise Configurations.
Expand "Email Content" tab.
Click on any email type and click "Edit" button in right panel.
Provide the "Subject" and "Body" and click "Save changes".
Click the "Reset to Default" button to discard your customizations and bring the content of all the emails back to their default.
Enterprise emails have been categorised into two main categories, they are:
Account Emails
Enterprise Invitation
Account Registered
Account Registration Completed
Account Activation Required
Reset Password
Reset Password Completion
Document Emails
Document Shared
Document Reviewed
Document Completed
Document Recalled
Sign-off Reminder
Post Processing
Document Signed
Document Declined
Document Updated
Send a Copy
Document Processed by Others
Document Processed by Me
Publish Workflow Completion Report
Comment Added to Document
Shared Space
Each email has got a distinct purpose in the SigningHub operations and workflows, and is sent to the users on a specific event. The names of these emails are precisely implying the events on which they are triggered.
The emails are comprised of particular placeholders which are automatically replaced with the predefined text (in the language file) upon sending. These placeholders are shown in CAPS within [ ]. The email templates along with their supported placeholders are given below:
Do not edit the text inside a placeholder otherwise they will malfunction.
Text shown in CAPS within [ ] are the placeholders (system variables) that are used in the email content. You must not edit these variables text. They will be replaced automatically with the predefined text from the language file, upon sending the email notification.
The enterprise users within your enterprise can overrule these enterprise email customizations through their personal email settings.
The emails sent from an enterprise account and from SigningHub to the enterprise users are branded as per the enterprise branding configurations, and will have the company defined customizations (i.e. header, footer, logo, etc.) in the email content.
The existing users who have upgraded their SigningHub to the latest release may click the "Reset to Default" button to get the new email types in the "Type" drop down.
SigningHub enables you to create certificate filters that could strain specific signing certificates for your enterprise users. This is useful when client side (local) signing is configured, and multiple certificates (software key, USB token/ SmartCard) are expected to appear at the time of signing. Hence, to make the certificate selection easy for the enterprise users, system will only show the required certificate(s) by processing these filters. In this way, an enterprise admin can restrict their enterprise users to use only those certificates for signing, which could pass the defined certificate filters criteria. You can manage (Add, Update, and Delete) these certificate filters as required.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Certificate Filters" under Settings options in Enterprise Configurations section.
Click "Add certificate filter" button.
Specify certificate Type, Field and Value for this filter. You can create a certificate filter on the basis of Issuer DN, Key Usage, SAN, Signature Algorithm OID, Policy OID, and QC Statements.
Click the "Submit" button.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Certificate Filters" under Settings options in Enterprise Configurations section.
Select the desired filter and click "Edit" in right panel.
Edit the required content (i.e. certificate Type, Field, or Value).
Click the "Submit" button.
Login with your enterprise admin credentials.
Click "Configurations" in left menu and click "Certificate Filters" under Settings options in Enterprise Configurations section.
Select the desired filter(s) and click "Delete" in right panel.
Again, click "Delete" in the confirmation dialogue.
You can create certificate filters on the basis of Issuer DNs, Key Usages, SAN, Signature Algorithm OIDs, Policy OIDs, and QC Statements.
In case of multiple certificate filters, SigningHub will use the AND operator among them to filter the required certificate(s) for signing.
The Enterprise Access Preferences tab lets you configure the account administration related SigningHub modules in a role. You can select your choice modules from the list to make them available to your enterprise users/ admins (registered with this role) for navigation. SigningHub supports granular access management along with their fine grained authorization, i.e. read, add/ edit, and delete access on different modules/ sub modules of the system.
Login with your enterprise admin credentials.
Click "Configuration" in left menu.
Choose "Roles" under People options in Enterprise Administration section.
Select the role to edit and click "Edit Role" in right panel. Role screen will appear for re-configurations.
Click "Enterprise Access Preferences". Select the user settings check boxes and their respective granular access as required.
Click "Save changes".
See the description in the "Enterprise Access Preferences" table below.
When you update a role in a production environment, the saved changes are available to the related users on their next login.
By default, the "Advanced Enterprise Reports" option will be disabled for all existing user roles.
The "Advanced Reports" will only be visible to the enterprise owner, and its child users (if the "Advanced Enterprise Reports" configuration is allowed against their role).
In case of , specify the call-back URL where the users could be redirected when they close a document in the iframe.
However for , specify a dummy URL to generate a Client Secret. As the call-back URL will not be required in the app configuration.
In this way when your enterprise document is shared with an external user through this integrated app, and they (external user) also sign it through this integrated app, SigningHub will supersede their personal/ enterprise signature settings with the ones defined in this role at the time of signing. The user roles can be managed from section.
Fields | Description |
---|---|
Webhooks and the Workflow Completion Report are configured in the document owner's enterprise settings | Webhooks and the Workflow Completion Report are configured in the integration settings of the recipient's enterprise | System Behavior Publishing Webhooks and the Workflow Completion Report |
---|---|---|
Events | Description |
---|---|
Email Type | Allowed Placeholders in Email Subject | Allowed Placeholders in Email Body |
---|---|---|
Fields | Description |
---|---|
Allow recipients to access documents via the email link without needing to log in
Enable this to allow the recipients accessing the documents without login via email links or integrated applications. When selected, following are business rules that will be followed:
Recipient comes via email link:
The enterprise recipients (that belongs to an enterprise) can access the shared documents simply by using their email links, based on the recipient's own enterprise settings. Conversely, if you don't select this check box, the recipients (inside this enterprise) will have to authenticate themselves into SigningHub, when they will use email link to access the shared documents that belong to this enterprise.
The individual recipients (that doesn't belong to an enterprise) can only access the shared documents (using their email links) by first authenticating themselves.
The unregistered users (that are treated as guest users), the users will always land on document viewer regardless of this check box status.
Redirect URL on Close/Finish
Field to specify a URL of any web-page where the recipients (coming via email link) could be redirected upon finishing their signing activity. If you leave this field empty, SigningHub will fallback to the default redirect URL as defined in SigningHub Admin. The redirection is based on the following conditions:
In case a recipient (registered or unregistered) is coming via email link to perform e-signature, then after finishing the signing activity, they will be redirected to this "Redirect URL".
In case the "Allow recipients to access documents via the email link without needing to log in" is enabled, and a recipient is coming via email link to perform signatures, then after finishing the signing activity, they will be redirected to this "Redirect URL".
In case the "Allow recipients to access documents via the email link without needing to log in" is disabled, and a recipient is coming via email link to perform signatures, then after finishing the signing activity, they will be redirected to the Document listing.
In case of any error appears while redirecting the user to callback URL on "Close/Finish", then a parameter (i.e. action=deleted) will be returned additionally in call back URL so a business application can consume that parameter to show any custom error page, based on following conditions:
If document owner is an enterprise user and a redirect URL configured under "Enterprise Configurations> Advanced Settings> Additional Settings> Redirect URL on Close / Finish".
If document owner is an enterprise user and there is no redirect URL configured under "Enterprise Configurations> Advanced Settings> Additional Settings> Redirect URL on Close / Finish", then the user will be redirected to redirect URL configured under "SigningHub Admin > Configurations > Global Settings > Redirect URL on Close / Finish".
If document owner is an individual user and a redirect URL configured.
If SigningHub login page is set as a redirected URL, then additionally a toaster message will also appear in case of an error on login page, along with action=deleted as a parameter in callback URL.
Webhooks
Specify a callback URL where SigningHub could send the HTTP POST update of each workflow. This is useful in those cases where all the configured recipients don't necessarily need to process a document package to complete their workflow. The workflow completion can be controlled by an external business application that could decide on need basis, whether to mark a document as complete or not after every major processing activity performed on it. When a URL is provided, this POST request provides the information of each workflow like:
Document Package
Document
Recipient
Action performed by the recipient on a document.
State of the Workflow
Next signatories
Type of Workflow
State of the document
Errors (Signing) SigningHub publishes an error webhook at the specified server URL for Go>Sign performed using the ADSS Server. These include:
The error that occurred when RUT is not configured.
The errors that occurred in Go>Sign Service and Go>Sign JS.
Check the below checkboxes for when you want the system to send a document processing report (XML) to the provided server address.
For document actions, when:
Shared
Signed
Declined
Reviewed
Meeting Host
Edited
Sent a Copy
Reminded
Recalled
Completed
Evidence Report Generated
Enterprise Document Deleted
For user actions, when:
Registered
Updated
Deleted
For errors, when:
Signing
The business application can then use the respective SigningHub API call to inform SigningHub that a workflow is complete and hence no need to send this document to the remaining recipients. Also while marking a workflow as complete, if any recipient of it has got this document in the "Pending" state, then SigningHub will delete the document from their inbox.
Workflow Completion
This area allows you to configure various activities (like document download control and report routing) upon workflow completion. The options included:
Allow workflow recipients to download the document only after workflow completion
Send the workflow completion report
Allow workflow recipients to download the document only after workflow completion
Enable "Allow workflow recipients to download the document only after workflow completion" to control when the Document Owner and recipients can download a document package and its containing document(s).
When enabled, the recipients and Document Owner will be allowed to download the document only after the workflow has been completed. In this case, if the recipient or Document Owner tries to download, then an error message will be displayed.
When disabled, the recipients or Document Owner will be allowed to download the documents in any status (e.g. Draft, In Progress, Pending, etc.) of the workflow, even if the workflow has not been completed yet.
Send the workflow completion report
Enable to automatically post the workflow reports (in XML format) to the configured address when the workflow completes. This applies to all users within your enterprise. When enabled, the "Server URL" and "Add completed document in report" fields are displayed.
Server URL
Select to specify the web server URL where you need to workflow completion reports are required to send. SigningHub gives you an option to publish Workflow Completion Reports along with the completed documents to a specific web server/URL. This configuration is at the enterprise level. The metadata and signed documents allow third party business applications to closely integrate with SigningHub and prevent the need to poll to check for complete status. For further details refer to "Publish Workflow Completion Report".
Add the completed document
Enable "Add the completed document" to receive the completed document along with the workflow completion report.
Add the workflow evidence report (WER)
Enable "Add the workflow evidence report (WER)" to receive the workflow evidence report along with the workflow completion report; else, leave empty.
Webhooks and the Workflow Completion Report are configured in the document owner's enterprise settings
Webhooks and the Workflow Completion Report are configured in the integration settings of the recipient's enterprise
System Behavior Publishing Webhooks and the Workflow Completion Report
Configured
Configured
The integration settings of the recipient's enterprise will be followed.
The enterprise settings of the document owner's enterprise will be followed.
Configured
Not Configured
The enterprise settings of the document owner's enterprise will be followed.
Not Configured
Configured
The integration settings of the recipient's enterprise will be followed.
Not Configured
Not Configured
The system will not publish the Webhooks and the Workflow Completion Report.
When the service plan stats have been reset
Service Plan
When the signature limit has been reached
Enable the toggles (i.e. On Screen and Email) to receive the on screen and email notifications(s) accordingly for Enterprise Owner, when 80% of the Constraint Limit of signatures is reached as per service plan.
When the simple electronic signature limit has been reached
Enable the toggles (i.e. On Screen and Email) to receive the on screen and email notifications(s) accordingly for Enterprise Owner, when 80% of the Constraint Limit of simple electronic signatures is reached as per service plan.
When the service plan has been changed
Enable the toggles (i.e. On Screen) to send the notification(s) accordingly to your Enterprise Owner, when your account's service plan is changed.
Payments
When an online payment has been received
Enable the toggles (i.e. On Screen) to send the notification(s) accordingly to your enterprise users, when the online payment against your enterprise account is successful.
Notify the enterprise user
When the forgot password flow has been initiated
Enable the toggles (i.e. On Screen and/or Email) to send the notification(s) accordingly to your enterprise users, when they click the "Forgot password" link.
When the account password has been changed
Enable the toggles (i.e. On Screen and/or Email) to send the notification(s) accordingly to your enterprise users, when they change their account password.
When there has been a failed login attempt
Enable the toggle (i.e. On Screen) to send the notification(s) accordingly to your enterprise users, when their login attempt is failed in SigningHub.
Notify document owner
When their documents have been processed by others
Enable the toggles (i.e. On Screen, Email/SMS, and/or Push) to send the notification(s) accordingly to the Document Owner, when their shared document is reviewed, updated, or signed by a recipient.
When their documents have completed
Enable the toggles (i.e. On Screen, Email, and/or Push) to send the notification(s) accordingly to the Document Owner, when their document workflow is complete.
When the documents are processed by them
Enable the toggles (i.e. On Screen, Email/SMS, and/or Push) to send the notification(s) accordingly to the Document Owner, when their shared document is reviewed, updated, or signed by a recipient.
With a daily summary email of all their pending documents
Enable the toggles (i.e. Email) to send a summary email to the document recipients from SigningHub, for all their pending documents on each day end, instead of sending individual email notifications for each document that is shared with them.
The summary email contains the total count of their pending documents along with the "Sign Now" button that will take them to the Bulk sign screen.
When there are subsequent changes in documents that they have received
Enable the toggles (i.e. On Screen, Email/SMS, and/or Push) to send the notification(s) accordingly to the document recipients, for every change (i.e. signed by other, annotated by other, reviewed by other, updated by other, commented by other, added approval or decline reasons by other, etc.) on the document, which they have processed earlier. However, in case of a new comment, SigningHub does not send a push notification.
Notify the recipients
When documents have been recalled from them
Enable the toggles (i.e. On Screen and/or Email/SMS) to send the notification(s) when you recall your document, either:
to pending recipients (all those document recipient(s) who haven't yet processed the document) or,
to all recipients (all those document recipient(s) who received the document, irrespective of whether they have processed it or not)
Account Emails
Enterprise Invitation
[APPLICATION_NAME][ENTERPRISE_NAME]
[USER_NAME][ENTERPRISE_NAME][ADMIN_NAME][ADMIN_EMAIL][APPLICATION_NAME]
Account Activation Required
[APPLICATION_NAME]
[USER_NAME][ENTERPRISE_NAME][ENTERPRISE_ADMIN][USER_EMAIL][APPLICATION_NAME]
Account Registration Completed
[APPLICATION_NAME]
[USER_NAME][USER_EMAIL][APPLICATION_NAME]
Account Registered
[APPLICATION_NAME]
[REGISTERED_BY][USER_NAME][USER_EMAIL][ENTERPRISE_NAME][APPLICATION_NAME]
Reset Password
[APPLICATION_NAME]
[USER_NAME][ENTERPRISE_ADMIN][PERIOD][APPLICATION_NAME]
Reset Password Completion
[APPLICATION_NAME]
[TIMESTAMP][USER_NAME][SUPPORT_EMAIL][USER_EMAIL][APPLICATION_NAME]
Document Emails
Document Shared
[APPLICATION_NAME][DOCUMENT_NAME]
[COLLABORATOR_NAME][OWNER_NAME][DOCUMENT_NAME][EMAIL_MESSAGE][OWNER_EMAIL]
Document Reviewed
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[COLLABORATOR_NAME][COLLABORATOR_EMAIL][OWNER_NAME][DOCUMENT_NAME][APPROVE_REASON][UPDATE_TIME]
Document Completed
[APPLICATION_NAME][DOCUMENT_NAME]
[DOCUMENT_ID][OWNER_NAME][DOCUMENT_NAME]
Document Recalled
[APPLICATION_NAME][DOCUMENT_NAME]
[COLLABORATOR_NAME][OWNER_NAME][OWNER_EMAIL][DOCUMENT_NAME]
Sign-off Reminder
[APPLICATION_NAME][DOCUMENT_NAME]
[EMAIL_MESSAGE][COLLABORATOR_NAME][OWNER_NAME][OWNER_EMAIL][DOCUMENT_NAME]
Document Post Processing
[APPLICATION_NAME][DOCUMENT_NAME]
[USER_NAME][DOCUMENT_NAME][DOCUMENT_ID][EMAIL_MESSAGE][OWNER_NAME][OWNER_EMAIL]
Document Signed
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[OWNER_NAME][DOCUMENT_NAME][COLLABORATOR_NAME][COLLABORATOR_EMAIL][UPDATE_TIME]
Document Declined
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[DECLINE_REASON][OWNER_NAME][DOCUMENT_NAME][COLLABORATOR_NAME][COLLABORATOR_EMAIL][UPDATE_TIME]
Document Updated
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[OWNER_NAME][DOCUMENT_NAME][COLLABORATOR_NAME][COLLABORATOR_EMAIL][UPDATE_TIME]
Send a Copy
[APPLICATION_NAME][DOCUMENT_NAME]
[DOCUMENT_OWNER][DOCUMENT_NAME][EMAIL_MESSAGE][COLLABORATOR_NAME][OWNER_EMAIL]
Document Processed by Others
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[USER_NAME][DOCUMENT_NAME][ACTION_PERFORMED][COLLABORATOR_NAME][COLLABORATOR_EMAIL][UPDATE_TIME][OWNER_NAME]
Document Processed by Me
[APPLICATION_NAME][DOCUMENT_NAME]
[USER_NAME][DOCUMENT_NAME][ACTION_PERFORMED][DOCUMENT_OWNER][DOCUMENT_OWNER_EMAIL][UPDATE_TIME]
Publish Workflow Completion Report
[APPLICATION_NAME][DOCUMENT_NAME]
[DOCUMENT_NAME][PACKAGE_ID][HOST_URL][ERROR_DETAIL]
Comment Added to Document
[APPLICATION_NAME][DOCUMENT_NAME][COLLABORATOR_NAME]
[USER_NAME][DOCUMENT_NAME][ACTION_COMMENT_ADDED][COLLABORATOR_NAME][COLLABORATOR_EMAIL][UPDATE_TIME]
Shared Space
[APPLICATION_NAME]
[COLLABORATOR_NAME][WORKSPACE_NAME][WORKSPACE_SHARED_OWNER_INFO][APPLICATION_NAME]
Enterprise profile management
Select this option to allow the enterprise profile configuration access in a role. This will enable the "Profile" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role. Also the users with this access can be marked as enterprise account owner, as they will be listed in the "Account Owner" tab of Enterprise>Profile for selection.
Users
Select this option to allow the enterprise users management access in a role. This will enable the "Users" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Roles management
Select this option to allow the enterprise roles management access in a role. This will enable the "Roles" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Groups
Templates
Select this option to allow the enterprise templates management access in a role. This will enable the "Templates" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Library
Select this option to allow the enterprise documents library management access in a role. This will enable the "Library" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Electronic Seals
Select this option to allow the use of electronic seals in a role. This will enable the "Electronic Seals" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Notifications
Select this option to allow the enterprise emails configuration access in a role. This will enable the "Notifications" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Billing
Select this option to allow the enterprise billing configuration access in a role. This will enable the "Billing" option under the profile drop down for the enterprise users/ admins belonging to this role, see details.
Application integrations
Select this option to allow the 3rd party integrations access in a role. This will enable the "Integrations" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Branding
Select this option to allow the enterprise branding configuration access in a role. This will enable the "Branding" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Reports
Select this option to allow the reports viewing access in a role. This will enable the "Reports" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role.
Documents
Select this option to allow the enterprise documents managing access in a role. This will enable the "Documents" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Logs
Select this option to allow viewing enterprise related activity logs in a role. This will enable the "Logs" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.
Advanced settings
Select this option to allow the advanced configuration access in a role. This will enable the "Advanced" tab under the "Enterprise Settings" option for the enterprise users/ admins belonging to this role, see details.