User Setup in Go1

Our standard SSO solution with CompliLearn (SLS) covers access for domain users but not authorisation to specific groups.

We recommend doing a full user import of all current AD users on launch to ensure that the list of staff is complete and staff who have not completed training can be easily identified. The csv import process also allows easy assignment to specific groups for different learning pathways.

Auto-provisioning

CompliLearn will auto-provision (create) accounts for users if they sign in with SSO. However, we recommend running a bulk upload of your users to initiate use of the system. There are a number of reasons for this recommendation:

• Auto-provisioning only creates accounts. It completes the user’s name and email address, and sets them up as a Learner. This means someone must regularly check the SLS and assign new users to learner groups and/or training courses, and update information such as additional roles, managers and Employee ID number. These details can be included in the CSV file.
  
  
• Uploading a full list of staff at the beginning allows for simple and accurate reporting. From within the SLS, it is easy to run reports on who has not accessed their assigned training. However, if you rely on SSO auto-provisioning, the database in the SLS must be compared against an external list of staff to find missing staff (i.e. staff who have never logged in)
  
  
• If any staff member already has an account with another training provider in Go1, auto-provisioning will not work.

The template CSV file can be downloaded from the Administer, Users screen. There is a button with three dots to the right of the “Create” button. Click this, then click “Import”, the template is linked at the bottom of the screen that opens.

I still want to depend on auto-provisioning

There is the occasional client who does rely on auto-provisioning and they accept the manual follow-up required. Also, the burden might be more manageable if you only rely on auto-provisioning ONLY for new staff and then complete an annual bulk upload to ensure the greater staff list in the product is current.

Its personal preference and if your staff go through a strict onboarding process, this may work in that respect. Where it can fall down is where onboarding puts a lot of responsibility on the new staff member as sometimes they might not login, even when asked.

How Bulk Upload Treats Existing Users

You should find this Support Hub page to be a helpful resource. It outlines how new information in the bulk upload will affect existing users in the system. Essentially you can use the bulk upload to ensure the staff within the product match an external list of all current staff and those who are left can be bulk made inactive.