The Import process provides an interface that allows the quick creation of multiple User records into Intelligentcontract. 

If you have a large number of Users that need to be created in your account, you should use the User import process rather than using the interface to type in the details of each User one by one. 

The User import is similar to all the other imports (e.g. for importing contracts, people, etc.), but the following points should be noted when importing Users.

1. A joining notification email will not be sent to the User at the point their user account is created. You will either have to:

  1. Inform each user of the temporary password that was assigned to their account. On first login they will be required to change this temporary password to something of their own choosing.
  2. Ask each user to request a "forgotten password" link from the login page. This will require them to know their username (generally their email address).

2. The import process does not stop you allocating a license to each User created when you have reached your subscription limit. It may be that after the Users have been imported, you do not have enough purchased licenses for all of them.  In this situation, your account will be placed into "limited status" (see My Account is "Limited". What does this mean?). 

Note: This does not apply to a concurrent usage or unlimited Users account - with these types of accounts, you are able to create and license as many Users as required.

Note: The User Import functionality does not allow for Transaction Type values of D - Delete. User records are required for Audit trial purposes and cannot be deleted. If a user should not have access to the account then you can remove their license by assigning the value of 'N' in the Assign License column.

Creating new Users via Import

First, generate a template .csv file for you to complete. Navigate to:

Configuration=>Manage Data = >Import

Select the template option of 'Users' from the drop-down list and press [Next]. You will be presented with the Upload Data File screen.

Here you can generate a Blank, Populated or with Example csv file. Select 'Populated', and then press [Generate] - your .csv file will be sent to the Batch Queue screen.

Fig 1 - Generating a User csv file

Your .csv file will contain rows for any existing Users that have been created for the account. The example below shows these values in green.

You are able to adjust the existing User information if required by using a transaction type value of M - Modification. You can adjust names and email addresses, alter User access (i.e. switch from Full User to a Read Only), remove or add Administrator rights, or even remove an assigned license.

Fig 2 - Populated User csv file

Note: You are unable to remove a license from a Key User. If tried, an error will appear during Import validation 

Along with modification, you can add new Users to your account using the Transaction Type of A - Add.

  • List all the new Users that are required at the bottom of the file.  
  • Leave blank the ID and original system reference columns. The system will generate new references for these new Users.
  • Mandatory requirements are the First and Last Name and Username. A Username is normally their email address.
  • 'Members of Security Groups' allocation will default to 'Everyone (rw)', meaning that the User you are creating will have access to all records.  If you have already created specific Security Groups and wish to allocate a new User to that group, so that they only see records allocated to that group, add the Security Group reference here (along with the (rw/ro) preferences).  To learn more about Security Groups click here.

Note: It is important NOT to remove the 'Everyone' Security Group from this column as this also controls what feature your Users see, if you remove the 'Everyone' Security Group then your User may not be able to see some features.

Note: Import validation will fail if you have entered the same Username multiple times.

  • Place a 'Y' or 'N' value in the Administrator, Assign License, and Read Only columns

Note: If you set the Administrator and Read Only columns to 'N', but Assign License to 'Y', this will create a Full User record with full read/write capabilities.

  • Add a Start and/or End Date if applicable
  • Copy the Security Group value 'Everyone (rw)' to the new lines

The Shadow and Supervisor columns can only be populated with User values that already exist. User values that have a Transaction Type of M - Modification allocated to them can be selected to be added as a Shadow or Supervisor to another User.

The below example shows that Bill Jones is to be shadowed by Susan Blue and Steph Williams Supervisor is to be John Green.

Fig 3 - Shadow & Supervisors

  • Copy the original system reference of the Shadow or Supervisor and place in the appropriate column - the Shadow and Supervisor ID values can be left blank.

If you have a requirement to have a New User Shadow or Supervise another User then you must first create the new User, and then do a M - Modification update to do this allocation (2 Imports).  Click here for more information regarding Shadow and Supervisor features.

Once you have completed your .csv file, Import, map, and validate as normal. Any errors will be displayed for you to adjust accordingly.

Once completed, all your new users will be created, and the system will have created a Person record for each of these new users.  Any modifications to user records will be processed.

Creating People records via User Import

The 'A' Add User import process will automatically create new People records for these new Users.  The two records are linked with the same OSR value.

We recommend when you are doing imports to import all your Users first and then the People records are automatically created for you.  

If you have done your People import first and then a User import then the system will create new People records and you could end up with duplicates - the original Person record will need to be deleted.

If there are remaining People that are not Users of the system they can be imported as normal via a Person import.

Note: When a User import takes place and a new Person record is created, the 'Party' field on the Person record is not asked for or populated.  The Party field on a User record links a Person to a Party (who they work for) it is important to ensure that all your Users are linked to an internal Party, if they are not linked then they are classed as an External person.

If you are using the 'Roles' option in Alerts, assigning an Alert to a Role instead of a named Person - Alerts will only ever be sent to Roles with 'Internal People' if your Users have not been linked to an internal Party then they will be classed as External People and will not receive the Alerts.

Note: When a user Import takes place and new Person records are created, their Person record will have the field 'Communication Enabled?' set to 'No' - this will need to be updated to say 'Yes' to allow system generated emails to be sent to this new User, such as Notes or Alerts.

Creating Users via the Import process does NOT trigger the automatic joining email that is sent out when manually creating Users. Once you have created these Users via import, it is recommended that you ask your Users to click on the 'Forgotten Password' option in the Sign In screen to trigger this email. Once they have reset their password, they will have access to the account.