Using the CSV Import feature will provide a simpler way to add, edit, and remove employees, managers, and admins in bulk. The data about Employees and users should be populated in the CSV files for Employees and all other Users (Admins, Managers etc.).

Please note that the data must be in a specific format to work and sync properly.

If you need to upload your Shift Schedule or Time Off Schedule via CSV files you will need to follow different steps:

CSV Templates

To upload the data on Employees or Users via CSV, you can use the provided templates for the Users and Employees, which are both necessary for this integration to work.

Each CSV file should be created exactly as per our template design.

Once this integration is active, templates can be found in Settings → Integration → CSV Import → Upload CSV, when you click on the Download Template buttons above the dialogs:

Important note

Any irregularities with the file’s format and with data contained in it will result in an error message during the upload process and an unsuccessful sync.
Both the Users.csv and Employees.csv files should be uploaded at the same time, otherwise, the upload cannot be initiated. Also, if you have only one admin, it should be added to the Users.csv file nonetheless - this file cannot be uploaded empty.

Employees.csv

The Employees.csv file is used to import Employees in bulk and perform changes such as deactivation, transfer into the right Teams, Team creation if it doesn't exist, etc.

Adding Employees with a company or personal device

To successfully register and identify employees with company computers, the employees.csv file requires one of two identification parameter sets:
- computer and user
- domain and user
Employees with personal computers are identified solely by their email address, which is a required field for this employee type.

The table below will help you populate the fields in the CSV files with values you may want to enter in each field. The No value in the table means that there is an option to leave the field blank when uploading the file.

Field	Possible Values
id	Alias ID No value
*type*	“personal” ”office”
*computer*	Computer name HWID No value
*domain*	Domain name No value
*user*	Username
*email*	Employee email No value
*name*	Full employee name
*title*	Employee title No value
*team*	Employee team No value (employee will be added to a default team)
*team_description*	Team description No value
*access_own_data*	”TRUE” ”FALSE”
*investigation_only*	”TRUE” ”FALSE”
*deactivated*	”TRUE” ”FALSE”

Example

Permissions fields

There are two fields in the Employee.csv that will set up your employees' permissions:

Access own data: If set to 'TRUE', this permission will allow employees to see their own utilization.
Investigation only: If there is a requirement to track some employees only for security purposes and only focus on their data, setting this option to 'true' places them in the 'Investigation Only' team, accessible only to admins.

Important note

All active employees must be included in this file, otherwise, if you exclude some of them, they will be automatically deactivated.

Users.csv

The Users.csv file is used to manage access to the Dashboard for Admins and Managers and to allocate their scope. The No value in the table below means that there is an option to leave the field blank when uploading the file.

Field	Possible Values
*email*	User email
*type*	“admin” ”manager”
*name*	Full name
*entity*	“all” (for admins) ”team” ”employee” "project"
*scope*	No value (for admins) Team name Employee name or email Project name
*scope_inheritence*	No value (for admins) “TRUE” ”FALSE”
*real_time*	No value (for admins) “TRUE” ”FALSE”
*screenshots*	No value (for admins) “TRUE” ”FALSE”
*screenshots_delete*	No value (for admins) “TRUE” ”FALSE”
*screenshots_ondemand*	No value (for admins) “TRUE” ”FALSE”
*screenshots_unblur*	No value (for admins) “TRUE” ”FALSE”
*recording_view*	No value (for admins) “TRUE” ”FALSE”
*recording_delete*	No value (for admins) “TRUE” ”FALSE”
*project_mngmt*	No value (for admins) “TRUE” ”FALSE”
*time_and_attendance*	No value (for admins) “TRUE” ”FALSE”
*approve_manual_time*	No value (for admins) “TRUE” ”FALSE”
*add_manual_time*	No value (for admins) “TRUE” ”FALSE”
*schedule_and_delete_shifts*	No value (for admins) “TRUE” ”FALSE”
*apps_and_websites*	No value (for admins) “TRUE” ”FALSE”
*activities*	No value (for admins) “TRUE” ”FALSE”
*activites_logs*	No value (for admins) “TRUE” ”FALSE”
*alerts*	No value (for admins) “TRUE” ”FALSE”
*labeling*	No value (for admins) “TRUE” ”FALSE”
*manage_org*	No value (for admins) “TRUE” ”FALSE”
*manage_billing*	No value (for admins) “TRUE” ”FALSE”
*add_teams*	No value (for admins) “TRUE” ”FALSE”
*invite_employees*	No value (for admins) “TRUE” ”FALSE”
*workload_distribution*	No value (for admins) “TRUE” ”FALSE”

Example

Scope fields

Entity: Scope determination
- For admins, it should be "all";
- For managers, it could be either "team", "employee", or "project";
Scope: Connected to the entity to better describe the scope:
- If the Entity is an employee, under Scope, you should put the name of the employee;
- If the Entity is a team, under Scope, you should put the name of the team;
- If the Entity is a project, under Scope, you should put the name of the project;
Scope_ineritance: This field is used to manage Scope inheritance, which needs to be turned on when configuring CSV Import integration, and it will allow the functionality of sharing / inheriting user scope from selected manager to others.

Permissions fields

Permission fields accept 'TRUE' or 'FALSE' values, controlling user access to specific features. For admins, these fields should remain blank, as they inherently possess full permissions.

Directory Integrations - CSV Import