The SafeWork Training Platform can utilize your company's HRIS data to ensure that user information is current on the platform. The information will be used to determine who will receive training, what kind of training they receive, and which location they are trained at.
Your StrongArm account rep will work closely with your Technical and HRIS team to ensure the data is structured in a way that resembles your company's 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 platform.
File Format and Naming
The data should be in a CSV file with headers. The file name can be anything if 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 analyses.
If no data exists for an optional field, please leave it blank in that row.
Starter Template Linked Below
|
Field |
Required |
Description |
|
username |
depends* |
The unique identifier for the user/employee. User IDs MUST be consistent across all of your StrongArm integrations. If you are using SSO, this should be the ID. *Required if no email is provided. |
|
first_name |
yes |
The user’s first name. |
|
last_name |
yes |
The user’s last name. |
|
department_name |
yes |
The department, facility, location, or warehouse where the user should be trained. Department Names MUST be consistent across all of your StrongArm integrations. |
|
|
depends* |
The user's email address. *Required if no username is provided. |
|
job_function_name |
yes |
The job function for the user in the SafeWork platform. This will help determine what content the user gets. |
|
job_title |
no |
A value representing the learner's job title should be used if the job title is free text and not deterministic of job function. Used in data analysis. |
|
supervisor_email |
yes |
The user's direct supervisor. This field must be the same source field as is used for user_id. |
|
employee_id |
no |
Optional unique identifier for user/employee used by client. If the employee is a wearable user employee_id is required. |
|
hire_date |
no |
Date user was hired. YYY-MM-DD format. |
|
shift_name |
no |
Optional shift for wearable user. |
|
password |
no |
Optional password for first-time basic auth users for training. |
|
language |
no |
The ISO_639-1 (https://en.wikipedia.org/wiki/ISO_639-1 ) language code that this learner prefers. |
|
roles |
no |
Comma-separated list of roles the user can have in StrongArm's applications. Allowable roles are: 'manager', 'shift_manager', 'learner_admin', 'learner_user', 'wearable_user' |
|
managed_department_names |
no |
Comma-separated list of departments a supervisor user manages. This is used for reporting filtering for training status reports. |
Data Delivery
Data will be uploaded to StongArm's FTP endpoint via a Secure File Transfer Protocol (sFTP) from the client. It can be delivered as often as needed for updates, but we recommend daily in the evenings. It will be processed once every 24 hours.
Authentication and Destination
Contact your Account Rep for an SFTP integration packet and credentials.