This article decribes different option to add, import or synchronize user data.
Register your users in the portal by adding them one by one, import from CSV-file, or synchronizing users from Microsoft Entra ID, Google Directory or by automated CSV-file downloads from an SFTP server.
To manually add users one at a time, go to Users > Add Users > Add New User.
The Nimblr System allows administrators to import user data using one of the following methods:
- Manually uploading a file in the Users section of the Nimblr admin portal.
- Pasting the file content as text directly into the Users section of the Nimblr admin portal.
- Automatically downloading the file from an SFTP server, enabling automated synchronization.
File Format Requirements for user import from file
- The file must be UTF-8 encoded, either with or without BOM (Byte Order Mark).
- The first row of the file must contain column headers that describe the data fields.
- The column order is flexible, meaning columns can be in any sequence.
- Data values must match the column headers they belong to.
- Supported delimiters: comma (,), tab (⇥), or semicolon (;).
- The file should not contain empty rows or extra spaces at the beginning or end of values.
Column Descriptions
Column Name | Required | Description |
---|---|---|
✅ Yes | The user's email address (must be unique for each user). | |
first_name | ❌ No | The user's first name. |
last_name | ❌ No | The user's last name. |
phone | ❌ No | The user's mobile phone number (optional but useful for certain features). |
group | ❌ No | The user group the individual belongs to (used for reporting, organizational and localization purposes). |
external_job_title | ❌ No | The user's job title |
external_department | ❌ No | The department the user belongs to, as defined in an external system. |
external_location | ❌ No | The user's work location (e.g., office location or city). |
external_country | ❌ No | The user's country of work or residence. |
external_company | ❌ No | The company name, useful if managing users across multiple organizations. |
manager_email | ❌ No | The email of the users manager or supervisor (used for reporting) |
external_id | ❌ No | External ID from directory service or other. |
Example User Import File
Below is an example of a correctly formatted user import file using a comma as a separator:
email,first_name,last_name,phone,group,external_job_title,external_department,external_location,external_country,external_company,manager_email,external_id |
jane.doe@example.com,Jane,Doe,1234567890,IT,Security Analyst,IT Security,New York,USA,ExampleCorp,mary.rose@example.com,124456 |
john.smith@example.com,John,Smith,9876543210,HR,HR Manager,Human Resources,London,UK,ExampleCorp,mary.rose@example.com,48300 |
Encoding and Compatibility
- The file must be encoded in UTF-8, which ensures compatibility with special characters and various languages.
- UTF-8 BOM is allowed but not required.
- Ensure the file does not contain hidden special characters, such as extra spaces or non-printable characters, which might cause issues.
Additional Notes
- Header row is required: The first row must contain column headers.
- Column order does not matter: Columns can be arranged in any order, as long as the headers match the data.
- Only "email" is mandatory: Other fields can be omitted if not needed, but first name and last name are recommended for better user identification.
- Delimiter consistency: The file must use the same delimiter throughout (comma, tab, or semicolon).
- No extra spaces: Avoid leading or trailing spaces in values.