Customer Pre-work
Examples of optional fields not already in portal you will need to request from your Implementation Project Manager at Go1:
Employee ID
Job Title/Role
Department
Region/location
Manager email
Hire Date
What if I make a mistake or need to add another field?
If you have already completed data mapping and have been directed to your AWS credentials, make sure to copy your credentials first.
Next navigate back to data mapping tab and click reset. You will now be directed to upload a new csv file. Make sure to add in any additional fields or update any spelling as needed before uploading again. You can now map the fields to Go1 fields again. Once you click done you are all set, there is no need to grab new AWS credentials.
Authorisation of user data feed service
Why do I need to authorise the Go1 data feed?
The data feed is a service provided by Go1 to keep your users in sync with an external system. By authorising the data feed you are allowing the data feed to update user accounts on your Go1 platform on your behalf based on the CSV file you are sending and data mapping you have elected.
What if I don’t know my password?
You can update your password in your portal under the account settings menu. If you are having trouble with this step please reach out to support.
CSV
How can I review an example CSV template for data mapping?
1. Select your user account icon from the top navigation, followed by the menu item Administer. From the Administration dashboard, select the tab Users: this will take you to Administer > Users report, a list of all of the users on your Go1 Platform.
2. Select the more button (...) from the top right of the Users tab, followed by Import From the Upload file popup, select the link: Click here to download sample .csv file.
3. A .csv file will download to your computer. Open the file in a spreadsheet application such as Microsoft Excel.
4. Review the column headers, this file is a template for the report you will create in your HR system.
What fields do I include in my CSV?
Provide fields in your CSV that exactly match the fields you will be sending from your system. You will match these fields to Go1 fields in the next step, data mapping.
Do I need to include any data in this CSV upload?
You can include 1 or 2 lines of dummy data as the information will not process and is only used for mapping purposes, but the layout of the file needs to be accurate.
What format is required?
CSV UTF-8 file format.
Data Mapping
What are ‘required’ fields?
The fields in your CSV file can have any name but you must map to certain fields on the Go1 side for the process to be successful. These required fields allow for the creation of or update to an existing user.
Data mapping required fields:
Email
First Name
Last Name
External ID: If using External ID for the unique identifier, External ID is an additional required field. This field is not a standard field in the Go1 LMS and you will need to request the field from your Go1 Implementation Project Manager.
Why would I use external ID as a unique identifier?
An external id from Go1 can be utilised as the unique identifier for the learner. This can be used to change a learner email when that email is a professional email change and the learner is only in the customer portal (no other Go1 portals). Please note that email is still a required field but all updates to the learner in the portal via data feed will be based on the unique id.
What are optional fields?
Some fields in Go1 are optional to map to because they are not required to create or update a user account. You may also choose to add additional fields to your portal based on the information you need to surface in user and enrolment reporting. In the case where you need additional fields, you will need to make a request to your Go1 Implementation Project Manager.
Optional fields which are already included in your portal:
1) Status – user status in portal. If you choose to map to this field, you will need to provide the values ‘1’ for active and ‘0’ for inactive. If you do not map to this field, it is recommended that you select the ‘auto-disable users checkbox under the status field option. By checking this box you are ensuring users will be made inactive when they are excluded from the file being sent to Go1.
2) Role – delineates a user role in the Go1 platform.
If you map to this role a pipe delimiter must be used to separate multiple values and these are the role values that can be used: "Learner|Manager|Content administrator|Administrator"
If you do not map to role all users will be created as learners (with the exception of manager see below). Any role given to the user in the portal after creation will not be changed by the data feed process ie: an Administrator will not lose their permissions.
3) Group – Map the group field if you would like to add users to a specific group in the Go1 portal. Adding a user to a group will assign learning contained in the group to the learner. Group is assigned via group number/ID.
4) Manager – Map the manager field if managers need to be assigned to users. Manager email must be supplied.
Can I assign more than one manager to a user?
More than one manager can be assigned to a user by separating values with a pipe delimiter: [email protected]|[email protected]
Do I need to map the role field to assign a manager?
If you are not mapping the role field then a user will gain the manager role in the portal when they appear in the manager field for the first time. They will also be assigned to the user as their manager going forward.
Are there any other fields I need to assign a manager?
It is not required, but recommended that you request a ‘Manager Email’ field is created. When mapping fields you can map the manager email from your side to both the ‘Manager’ (assigns the manager) and the ‘Manager Email’ field (surfaces manager email for the user in portal for ease of reporting.)
How do I remove a manager from a user?
If a new manager is sent through the data feed it will replace the current manager in the Go1 portal.
AWS S3 Bucket creation
My AWS s3 bucket and folder
Once you finish your data mapping for the first time, an AWS s3 bucket and folder and
AWS credentials
You will be directed to copy these credentials as soon as you finish data mapping. Here is an example of what they will look like:
AWS S3 bucket path - s3://go1-user-feed-production/{{portal-id}}/
Key Pair - Client ID: dfehapeeni183hdljan | Secret Key: dh34jdu3j4id3l2k
Why do I need AWS credentials?
The AWS credentials is the information needed to send your data feed file to Go1. This is like a user name, password and address for where your file is being sent to.
What if I forgot to copy my credentials or I lost the credentials?
Within the data feed page in the portal, navigate to Configuration > AWS credentials tab. Check the date of credential generation, does it look recent and like maybe another member of your team could have them? If no, Click regenerate AWS credentials button. Save the new credentials and ensure these credentials are updated on your side so that you can send Go1 your data feed file.
Upload History
What can I see here?
Progress of uploaded file
How many users have been created
How many users have been updated
How many users did not process
Downloadable report containing any issues or errors and all updated users
Error message key coming soon