Jump to a section
Prepare your file
2. Column Headers & Required Fields
3. File Formatting & Unused Columns
Import & review
Use Spreadsheet Import to add employees or update multiple user records at once. Company Admins can manage names, teams, roles, managers, locations, anniversaries, and other employee information with a single file.
1. Before You Begin
You must be a Company Admin to import users. Start with the current Recognize template and include only the columns you intend to update.
Download the Spreadsheet Import Template
For an automated employee roster sync, see the Recognize SFTP Integration Guide. Manual imports use the options you select on the Import page; review these options before each upload.
2. Column Headers & Required Fields
Required Fields
For email-based accounts, include Email, First name, and Last name. Employee ID is optional but recommended as a stable account identifier.
If an employee does not have an email address, a phone number is required. Phone-only accounts are available only on the Enterprise plan when phone-only accounts are enabled in your admin settings.
Standard Fields
All columns included in the Recognize template are fully supported. Keep the column headers exactly as they appear in the downloaded template, including the optional labels. The current template includes:
| Column Header | What to Include |
|---|---|
| Employee id(optional) | A stable employee identifier; recommended for matching existing accounts. |
| The employee’s email address. | |
| First name | The employee’s first name. |
| Last name | The employee’s last name. |
| Display name(optional) | The employee’s display name. |
| Preferred first name(optional) | The employee’s preferred first name. |
| Job title(optional) | The employee’s job title. |
| Phone(optional) | The employee’s unique phone number. |
| Team(optional) | Team assignments. Separate multiple teams with commas. |
| Roles(optional) | Company Role assignments. Separate multiple roles with commas. |
| Start date mm/dd/yyyy(optional) | The employee’s start date in MM/DD/YYYY format. |
| Birthday mm/dd(optional) | The employee’s birthday in MM/DD format, without a year. |
| Manager Email(optional - must be users in Recognize) | The email associated with the manager’s Recognize account. |
| Country(optional) | The employee’s country. |
| Location(optional) | The employee’s work location. |
| Department(optional) | The employee’s department. |
| Locale(optional) | A supported locale code or accepted language label. |
| Address(optional) | The employee’s address. |
Custom Fields (Enterprise Only)
Enterprise customers may add up to 10 custom fields. Contact support@recognizeapp.com to arrange custom fields before adding columns outside the standard template.
3. File Formatting & Unused Columns
- Use the current template and keep its column headers unchanged.
- Put first and last names in their separate columns; do not enter a comma-separated full name in one field.
- Format dates as text/string values so the file retains the required format.
- Only Team and Roles support multiple values. Separate values with commas, for example: Engineering,Leadership.
- Keep Employee IDs, email addresses, and phone numbers unique within your company’s Recognize account.
- Make sure each manager email matches the manager’s Recognize account. If the manager is new, include their own employee record in the import.
| Date Field | Required Format | Example |
|---|---|---|
| Birthday | MM/DD (no year) | 05/25 |
| Start Date | MM/DD/YYYY | 05/25/2026 |
Delete unused columns. If you are not updating an attribute, remove its column entirely. A column that is included but left blank can overwrite previously uploaded data. If a field is managed through an ongoing user sync or SFTP file, the next sync can overwrite manual changes.
4. How Recognize Matches Your Records
Recognize identifies employees using the first available identifier from this list:
- Employee ID (recommended)
- Phone number
If a matching email account does not yet have an Employee ID, an import can add the Employee ID to that existing record. Keep identifiers consistent to avoid creating duplicate profiles.
Updating an Email Address
Use the employee’s existing Employee ID when updating their email address. Without a stable matching identifier, a new email can be treated as a new account. If Remove Users is selected, the previous account may also be disabled if it is no longer in the file.
Changing an existing Employee ID requires Support. An Employee ID cannot be changed through an import once set. Contact support@recognizeapp.com to have Engineering clear the old ID before importing the corrected value. For duplicate accounts, provide the employee’s name, old and new email addresses, and the account to keep.
Flow Chart for User Lookups
5. Supported Locale Codes
If you include the Locale field, enter one of the 22 supported locale codes or accepted language labels below. Copy the value exactly as shown, including capitalization, hyphens, accents, and parentheses. Do not include quotation marks.
Use locale codes for a simpler import file. For the full reference, see Supported Languages & Locale Codes.
| Language / Region | Locale Code | Accepted Language Label |
|---|---|---|
| Arabic | ar |
(Arabic) العربية |
| Chinese (Simplified) | zh-CN |
中国人 (Chinese Simplified) |
| Chinese (Taiwan) | zh-TW |
中國人 (Chinese Taiwan) |
| Danish | da |
Dansk (Danish) |
| Dutch | nl-NL |
Nederlands (Dutch) |
| English (Australia) | en-AU |
Australian English |
| English (Great Britain) | en-GB |
Great Britain English |
| English (United States) | en |
United States English |
| French | fr |
Français (French) |
| French Canadian | fr-CA |
Canadien français (French Canadian) |
| German | de |
Deutsch (German) |
| Hindi | hi |
हिन्दी (Hindi) |
| Italian | it-IT |
Italiano (Italian) |
| Japanese | ja |
日本 (Japanese) |
| Mongolian | mn |
ˈmɔ̙̃ɴɢɞ̜̆ɮ çe̝ɮ (Mongolian) |
| Norwegian | no |
Norsk (Norwegian) |
| Polish | pl |
Polski (Polish) |
| Portuguese | pt |
Português (Portuguese) |
| Spanish | es |
Español (Spanish) |
| Swedish | sv-SE |
Svenska (Swedish) |
| Thai | th |
ไทย (Thai) |
| Vietnamese | vi |
Tiếng Việt (Vietnamese) |
Invalid locale values may be ignored or reported as an import error. See the Locale error resolution below.
6. How To Import a Spreadsheet
- Click Menu in the upper right corner of Recognize.
- Select Company Admin.
- Select Users from the left navigation.
- Select Import from the top-right menu.
- Download the sample spreadsheet, fill in the fields you intend to update, and remove unused columns.
- Select Choose File and choose your completed spreadsheet.
- Review the import options below. Run a Dry Run first to check potential changes and errors.
- When you are ready to make changes, uncheck Dry Run and select Import.
7. Import Options & Dry Run
| Option | What It Does |
|---|---|
| Update Only | Updates users found in Recognize. New users in the file will not be added. |
| Remove Users | Updates users in the file and disables users who are not present in the file. Review your roster carefully before selecting this option. |
| Dry Run | Checks the file and reports potential changes or errors without making changes. Uncheck it when you are ready to run the actual import. |
| Send Invitations to new users | Automatically sends invitations to users added by the import. If this is not enabled, new users remain in a pending invite state and can be invited later. |
By default, the import adds new users and updates existing user information. The options above change that behavior.
Before selecting Remove Users: Make sure your file contains the full set of users you intend to retain. Leave this option unchecked when uploading a partial file for targeted updates.
8. Review Your Import Results
- Your import is queued and processed in the background.
- Stay on the Import page to watch progress, or leave the page while processing continues.
- You will receive an email when the import is complete.
- If errors occur, a results spreadsheet is available from the completion email and the Last Import section on the Import page. Review the affected records and error messages before uploading corrections.
You can also access uploaded files under Company Admin > Documents > Uploads and error downloads under Company Admin > Documents > Downloads.
9. Summary Checklist
- Use the current Recognize template.
- Include required fields and keep identifiers consistent.
- Keep headers unchanged and remove unused columns.
- Use the correct date formats and supported locale values.
- Separate multiple teams or roles with commas.
- Check manager emails and include new manager accounts as needed.
- Run a dry run and review the report.
- Confirm Update Only, Remove Users, and invitation settings before importing.
- Uncheck Dry Run when ready to apply changes.
Common Manual Spreadsheet Import or SFTP Errors
Manual spreadsheet imports and SFTP files can encounter the same record-matching and formatting errors. Before troubleshooting, compare the employee’s email, Employee ID, and phone number in the file with their Recognize account. Check for typos, duplicate values, and identifiers paired with different accounts.
Error Code Descriptions and Resolutions
Find the error in your upload report below, then follow the fix steps. Account identifier errors require help from Recognize Support; formatting errors can usually be corrected in your file.
Email has already been taken
What it means
The email in your file already belongs to an account with a different Employee ID.
How to fix it
- Compare the employee’s email and Employee ID in your file with their existing Recognize account.
- Email support@recognizeapp.com with the correct Employee ID and ask for the old ID to be cleared by Engineering.
- If there are duplicate profiles, specify which profile to keep and which to merge or remove.
- Make sure your file matches the active account and correct Employee ID before the next import.
Example
The file lists John.Smith@Recognizeapp.com with ID CF456, but the existing account uses ID AB123.
Employee ID cannot be modified once set
What it means
The email and Employee ID in your file already exist in Recognize, but on two different accounts.
How to fix it
- Email support@recognizeapp.com and request that Engineering clear the old Employee ID.
- Confirm the correct email and Employee ID pairing. Keep the email unchanged when adding the corrected ID in the next import.
Example
The file pairs John.Smith@Recognizeapp.com with AB123. In Recognize, that email uses CF456, while AB123 belongs to John.Smith.2@Recognizeapp.com.
Duplicate entry error
Report message:Mysql2::Error: Duplicate entry 'User@domain.com-domain2.com' for key 'index_users_on_unique_key'
What it means
A previously merged or soft-deleted account may still exist in Recognize’s back end, even though you cannot see it.
How to fix it
- Check whether the email or Employee ID already exists in your company account.
- If you cannot find it, email support@recognizeapp.com to confirm whether the account was soft-deleted.
- If confirmed, give the team permission to archive the old email address so it can be updated in the next import.
Example
John.Smith@Recognizeapp.com was soft-deleted during a merge. Importing that email for a new user can trigger a duplicate entry error.
Start date invalid / birthday invalid
What it means
A date in your file does not match the required format.
How to fix it
- Format date values as strings, following the sample spreadsheet.
- Use MM/DD for birthdays, without a year, and MM/DD/YYYY for start dates.
- Keep the date format consistent throughout the file.
Example
For a May 25 birthday, enter 05/25 instead of 25 May.
Phone already taken
What it means
Two employees in your file share the same phone number. Phone numbers must be unique in Recognize.
How to fix it
- Find the duplicate phone number in your file.
- Correct the entries so each employee has their own unique phone number.
Example
John Smith and Jane Doe are both listed with 555-5555.
Formatting issue
What it means
One or more values do not follow the import template’s format.
How to fix it
- Compare the affected row with the sample spreadsheet.
- Put first and last names in their separate columns, rather than using a comma-separated name.
- Format dates as strings and use the required date formats.
Example
Enter John in First Name and Smith in Last Name, rather than Smith, John in one name field.
Unsupported Locale
Report message: Locale ‘example’ is not one of the supported locales
What it means
The Locale column contains an unrecognized value.
How to fix it
- Choose a code or accepted language label from Supported Locale Codes.
- Copy one value exactly, including capitalization, hyphens, accents, and parentheses. Do not include quotation marks.
Example
Use fr-CA or Canadien français (French Canadian) for French Canadian. Use vi or Tiếng Việt (Vietnamese) for Vietnamese. The value tx is not supported.
Manager email not found
What it means
Recognize could not find a manager account matching the manager email listed in the employee’s row. The email may not match the manager’s Recognize account, or the manager may not have an account yet. During a dry run, this error can also appear when the manager is included in the file but has not yet been added to Recognize.
How to fix it
-
If the manager already has a Recognize account:
Check the email associated with their account. Make sure the manager email in the employee’s row matches that email exactly, then correct the file if needed. -
If the manager does not have a Recognize account:
Create an account for the manager, either by adding them to your user import or creating the account in Recognize. Use that account’s email as the manager email in the employee’s row so Recognize can link the employee to the correct manager.
If you are running a dry run
A dry run checks the file without creating accounts. If the manager is included in your file but does not yet exist in Recognize, this error may appear until you run the actual import.
- Go to Company Admin > Users.
- Select Import in the top right tertiary menu.
- Check Last Import > Dry run. True means the last upload was a dry run. Confirm that the manager is included in the file and that the manager email in the employee’s row matches their email in the file.
- Once the rest of the file is correct, uncheck the dry-run box and run the import to create the manager’s account and link the employee.