This article is intended for Administrators.
In order to optimize and centralize all the data related to your employees, you can, before launching the interface, import the history of your past training sessions.
💡 Please note that this import can only be done before the launch of the platform.
By doing so, the content available during the reviews you will conduct on Elevo will be enriched, hence making it easier to get started and use the interface.
📥 Import your past training sessions
- Download our spreadsheet template (Excel, Google Sheet, CSV),
- Fill in the document,
- Send it to Elevo Support (support@elevo.io).
🗒 File format for transferring the data
The file must respect the following rules:
- RFC 41802 for CSV format compliance,
- Be encoded in UTF-8 format,
- The first line will define the column headings,
- Must contain all the mandatory columns,
- Optional columns are not mandatory,
- Any unrecognized columns will be ignored,
- The columns can be in any order.
CSV file columns
| Column header | Mandatory / Optional | Restrictions | Details |
| login | Mandatory |
Strings of characters
Must be unique across all users |
Unique identifier for a user: Either the user's email Or the user's username |
| request_title | Mandatory | Strings of characters (Max 150 characters) | Summary of the training request |
| additional_information | Mandatory | Strings of characters |
Additional information on the training request |
| training_request_period | Mandatory | Strings of characters | Period on which the training was carried out (Example: "2022") |
| request_approbation | Optional | Possibles values: - waiting_for_approval - approved - refused |
Approval of the application |
| manager_priority | Optional |
Possibles values: - low |
Manager priority |
| created_by | Optional |
Strings of characters |
Login of the creator of the request (see the first column) |
| requested_at |
Optional |
In format ISO 8601 (ex: 2015-02-25) |
Date of creation of the request |
| individual_cost | Optional |
Strings of characters |
Individual cost of training |
| funding_source_X.title | Optional |
Strings of characters |
Source of funding |
| funding_source_X.amount | Optional |
Strings of characters |
Amount of funding source |
| training_session_name |
Mandatory if session and/or funding information is filled in) |
Strings of characters |
Name of the training session |
| training_organization |
Optional |
Strings of characters |
Name of the training organization |
| format | Optional |
Possibles values: - remote |
Training format |
| type | Optional |
Possibles values: - inter |
Type of training |
| duration | Optional |
Strings of characters |
Duration of the training (in hours) |
| start_date | Optional |
In format ISO 8601 (ex: 2015-02-25) |
Start date |
| start_time | Optional |
Strings of characters |
Start time |
| end_date | Optional |
In format ISO 8601 (ex: 2015-02-25) |
End date |
| end_time | Optional |
Strings of characters |
End time |
| location | Optional |
Strings of characters |
Location of the training |
| training_session_period |
Mandatory if session and/or funding information is filled in) |
Strings of characters |
Period on which the training was carried out (Example: "2022") |
📐 Basic requirements when importing
- If the date is set but not the time, the time will be set by default to Midnight UTC, meaning 1am on the interface.
- Time must always be given in UTC. The interface will interpret time using the UTC time zone and then translate and display the time according to the relevant time zone.
- For example: if the start date in the file is 2022-12-03 with a time set to 8:30, the interface's session will consider that it has begun at 9:30 on December 3rd.
- If the start date is filled in, the end date becomes mandatory and vice versa.
- If the "requested_at" column is empty, by default it will consider the date of import.
- If the "created_by" column is empty, by default it will be filled in with the name of the most senior Admin listed on the interface (the one created at the earliest date and currently active).
- If left empty, the default value for "request_approbation" will be "waiting_for_approval".
- If left empty, the default value for "manager_priority" will be "medium".