Skip to main content
General tips: 1. Please ensure the entire file is formatted as text before uploading it. 2. Do not use any spaces or special characters (e.g. ä, ß or é) in emails. 3. It is important that the same values are written exactly the same Example: Köln, köln, koeln = these will be evaluated as three different values and create a problem when analysing your data as they will appear as 3 filters instead of 1. 4. If an attribute of an employee is missing (excluding a “Role”), this employee will still be uploaded. If an attribute has an empty value in the file, the attribute of this employee will be set to empty as well. Mandatory fields: ImportId, Email, Firstname, Lastname, Language must be present in your import file and contain values for each of your employees. Upper and lower case and extra spaces in the column headers do not matter, but the spelling does: “email” or “EMAIL” is recognised as Email, whereas “First Name” is not recognised as Firstname. ImportId - Identifies each individual employee in your organization and must be unique. Existing employees will be recognised using this and can be updated during import even if their email has changed. e.g. their HR ID. Email - These must not contain any spaces or special characters (such as ä, ß or é). “@norealmail.com” is used in Code Participation cases. Language - The main language of the employee, which is used to select the language of notifications and questions. Needs to follow ISO 639-1 format. See ‘Language Codes’ tab for a full list. Optional fields: Role - Optional: If the role column is present, you must specify a role value for each employee. Possible roles are: Admin, Manager, Analyst, Report viewer, Respondee (see here for more information). Upper and lower case do not matter, so “Report Viewer” works just as well as “Report viewer”, but the spelling must be right. A row with an unknown role value is skipped, while the rest of the file is imported as normal. Emails to Report viewers, analysts, managers and admins are sent from the system automatically, as soon as this column is uploaded, enabling them to access the account immediately. ReportsToId - Optional: Contains the ImportId of this employee’s direct supervisor. Can be left empty if employee has none. PermissionGroup - Optional : Contains the attribute for which the employee can view data. e.g. “Country”. PermissionGroupValue - Optional: Contains the value of the PermissionGroup for which the employee can view data. e.g. “Germany”. Enter a ’*’ here to give this user access to all data. Employee attributes (automatically grouped) - Optional: Add a column headed Age Category and/or Seniority and enter the year in YYYY format. We use these to calculate the employee’s age group and seniority group automatically. Your own company’s attributes - Optional: The column headings are the names of your attributes. These will later become the filters in your dashboards. A column heading can be at most 100 characters long. If it is longer, only that column is left out and you get the message “Column … was not imported as an employee attribute because the column name must be between 1 and 100 characters long.” — every employee is still imported. An attribute also cannot be named like one of the fixed columns above: Attribute Management will not let you create an attribute with such a name or rename one to it. Decide now which aspects you want to analyse after your survey, and make sure you’ve created the right attributes to do so.
Spelling of the column headers: For the fixed columns ImportId, Email, Firstname, Lastname, Language, ReportsToId, Role, PermissionGroup and PermissionGroupValue, as well as Age Category and Seniority, upper and lower case and extra spaces are ignored — “REPORTSTOID” or “ReportsToID” counts as ReportsToId. The spelling still has to be right: if a mandatory column is missing as a result, the import stops with a “missing mandatory fields” error. An optional column spelled differently, such as “Reports To Id”, is created as an ordinary employee attribute instead.Each column only once: If a column header appears twice — even if the two differ only in upper and lower case, such as ReportsToId and “REPORTSTOID” — the whole import stops with the message “The file has more than one column named …”. Delete one of the two columns and import the file again.
Some examples of these are:
Country Region Location Department Team Gender Position (Management/Employee/Trainee etc) Contract (full/part-time) Code (example used for Code Participation - for employees without email addresses)
Although you upload an individual data set for each employee, an anonymity threshold is used to determine whether an employee’s feedback can be analysed.
Here is further information and a video about the Excel import.