Worklete integrates with your company HRIS system to ensure that user information is up to date on the Worklete platform and to enable SSO integrations for a streamlined login process. We utilize this information to determine who will receive training, what kind of training they receive, and which location they are trained at.
Your Worklete account rep will work closely with your Technical and HRIS team to ensure the data is structured in a way that resembles your companies existing reporting and organization structure.
The information below will provide insights for your technical team to scope the time and resources needed to set up an integration with the Worklete platform.
File Format and Naming
The data should be in a CSV file with headers. The file name can be anything as long as it is unique and contains no special characters (except for underscore). We suggest naming it users_
Data Description
Note: Old data will be overwritten by new data.
Each File should:
- Contain no duplicate user_ids.
- Only contain active users, if a user is on leave or has left the company, please filter them out.
Data Field Definitions
These are the specific fields that our system uses. Feel free to include any additional fields you choose, they will be stored in their raw data format for use in further and more complex analysis.
If no data exists for an optional field, please leave it blank in that row.
Starter Template Linked Below
|
Field |
Required? |
Description |
|
user_id |
yes |
The unique identifier for the user/employee. User IDs MUST be consistent across all of your Worklete integrations. If you are using SSO, this should be that ID |
|
first_name |
yes |
The user’s first name |
|
last_name |
yes |
The user’s last name |
|
location_id |
yes |
The location that the user should be trained at. Location IDs MUST be consistent across all of your Worklete integrations |
|
|
no |
The user's email address |
|
team |
no |
The job function for the user in the Worklete platform. This will help determine what content the user gets. Example: Transportation vs Warehouse |
|
job_title |
no |
A value representing the learner's job title, this should be used if the job title is free text and not deterministic of job function. Used in data analysis |
|
language |
no |
The ISO_639-1 (https://en.wikipedia.org/wiki/ISO_639-1 ) language code that this learner prefers. |
|
supervisor |
yes |
The user's direct supervisor |
Data Delivery
Data will be uploaded to AWS S3 via API access. It can be delivered as often as needed for updates. It will be processed once every 24 hours.
Authentication and Destination
Contact your Account Rep to setup your AWS key and receive a S3 destination for data.