The employees can be provisioned via a CSV file that gets pushed via SFTP to the Honestly server. Based on the CSV file new employees will be added, not existing employees will be removed and information of already existing employees will be updated. This option is available to Enterprise or Global Player Customers.
Authentication works via public key authentication. A public key needs to be shared with Honestly to the email address firstname.lastname@example.org.
A username will be provided by Honestly that can then be used in combination with the private key of the public key to push the CSV file to the Honestly server.
The file name needs to be `employees.csv`.
The file needs to be encoded with UTF-8 character set without any BOM.
The data in the file itself needs to be separated by the comma character and surrounded by double-quotes.
The column names need to be included in the CSV file in the first line. The order of the column names is irrelevant.
The following columns need to be present in the CSV file and also all dataset must contain values for them.
|ImportId||String||The unique identifier of an employee will be used to identify employees that have left the company. Furthermore, the identifier will match existing employee data with the data in the file even when the email address has changed.|
||String||The E-Mail Address of the employee.|
|Firstname||String||The first name of the employee.|
|Lastname||String||The surname of the employee.|
It's recommended to also provide the language of the employee. If the language can not be provided we can configure a default language.
|Language||ISO 639-1||The primary language of the employee that will be used to select the questions and notification language of the employee. See here for more details.|
Optional additional employee groups
Based on the configuration of employee groups in the web application, additional employee data can be included to receive more detailed insights. Therefore the CSV file needs to be extended with these additional columns in String data format.
On the web application the user can select which employee data should actually show up as a filter on the dashboard.
Optional role & permission related columns
Employees have access to results based on their reports to relationship in addition to the permission on specific employee groups. ReportsToId or PermissionGroup and PermissionGroupValue can be blank.
Value needs to be based on the table "Available roles". If no role is assigned (blank field) the employee will only be able to take part in surveys but will not be able to e.g. login to see results or create surveys.
|ReportsToId||String||Contains the ID (ImportId) of the employee that this employee reports to.|
|PermissionGroup||String||Contains the name of the column header which drives the employee's permission. e.g. Country.|
Contains the specific employee group the user has access to e.g. Germany
use `*` to give access to all users
|Admin||Can do everything and has access to all account data. PermissionGroups are not taken care of.|
|Manager||Can manage surveys & dashboards associated with their user groups specified in the PermissionGroups and Hierarchy.|
|Analyst||Has read access to specific dashboards associated with their user groups specified in the PermissionGroups and Hierarchy.|
Example file with a department and location employee group
This file is imported twice a day (around 4.a.m and 4 p.m.). After a successful import, the import file is removed from the folder.
Warning: If you choose the automatic upload all manual changes will be overwritten every 12 hours