Register enterprise users via CSV file
Last updated
Last updated
© Ascertia Limited 2024
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 |
|---|---|
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. |
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.
| Field Name in SigningHub | Supported Header in CSV |
|---|---|
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 |
