| User ID | Required - A unique identifier for the user. This is the internal balkan id of the user |
| Full Name | One of Full Name, First Name, or Last Name required - The user's full name. This is the recommended name field to use. In the sample CSV, this is: Ahmed Ali, Maria Gomez, etc. |
| First Name | One of Full Name, First Name, or Last Name required - The user's first name. Using Full Name is recommended, but First Name can also be provided. In the sample CSV, this is: Ahmed, Maria, etc. |
| Last Name | One of Full Name, First Name, or Last Name required - The user's last name. Using Full Name is recommended, but Last Name can also be provided. In the sample CSV, this is: Ali, Gomez, etc. |
| Work Email | Required - The work email of the user. In the sample CSV, this is: aali@example.com, mgomez@example.com, etc. |
| Department | Optional - The user's department. In the sample CSV, this is: Sales, Marketing, etc. |
| Title | Optional- The user's job title. In the sample CSV, this is: Sales Representative, Marketing Manager, etc. |
| Start Date | Required - The user's start date in MM/DD/YYYY format. In the sample CSV, this is: 01/21/2021, 07/13/2020, etc. |
| End Date | Optional - The user's termination date, if any, in MM/DD/YYYY format. In the sample CSV, there are no End Dates listed, meaning everyone is still with the company. |
| Employment Type | Optional - The type of employment. In the sample CSV, this is: Full-time, Part-time, etc. |
| Manager | Optional - The full name of the user's manager. In the sample CSV, this is: Maria Gomez, Ahmed Ali, etc. |
| Manager Work Email | Optional - The work email of the user's manager. In the sample CSV, this is: mgomez@example.com, aali@example.com, etc. |
| Source User ID | Optional - A unique identifier for the user from the source system. This can be a number or a string. In the sample CSV, this is 23, 3251, etc. |
| BalkanID Roles | Required - Roles of the User in the Balkan ID application. Can be - reviewer, riskmanager, admin |
| Organization | Optional - The organization the user belongs to. |
| Metadata Version | Optional - The version for the Metadata. The only supported version as of now is v1. The Metadata fields supported in v1 are - location (json - address (string)), role id (string), user (string), manager id (string), manager name (string), app (string), correlation id (string), tenant (string), timestamp (string). Even though the following fields are supported, they are meant for internal use and are only supported for the purpose of being able to download from an User integration (like Finch or Google) and then upload after edits to the User without losing relevant information about the original extraction from the integration - app (string), correlation id (string), tenant (string), timestamp (string). |
| Metadata | Optional - Metadata that is to be added to the User. This is a JSON object (see examples). Currently only Metadata of version v1 is supported. |