Select an Employee Identifier

In this article, we'll walk account admins through how to select an Employee Identifier. Your company can use either email or employee ID to identify employees in 15Five.
 
In this article, you will learn...

Change your company's Employee Identifier

Email is the default Employee Identifier in 15Five. Follow the steps below to change your company's Employee Identifier.

  1. Click on the Settings gear in the top, right-hand corner of 15Five.
    Open
  2. Select 'Company settings' from the dropdown menu.
    CompanySettings.png
  3. Click the arrow to the right of "Import settings" to expand that section.
    Import-Settings.png
  4. Select your desired Employee Identifier— either Employee ID or Email.
    Select-UID.png

FAQs

Why should I use employee ID, rather than email address, as the unique identifier for my company?
A person's employee ID is a static, unchanging form of identification, whereas their email address has the potential to change (such as in the case of a name change or a company domain change). By identifying your employees in 15Five by their employee ID, you prevent the chance of people losing access to their 15Five account and/or accidentally creating a duplicate 15Five account following an email address change.
Do I need to include an email address for a user if my company uses employee ID as our identifier?
Yes— reason being, employees must sign in with an email address, and if we don't have one on record for them, they cannot log in.
What is the default unique identifier in 15Five— email or employee ID?
Email is the default.
What happens if my company switches to use employee ID as our unique identifier and then we do a bulk import to populate employee IDs in 15Five? Will duplicate accounts be created?
No— to prevent this from happening with CSV imports, we created logic for the system to check both email and empty ID. If there are empty IDs or duplicate IDs between 15Five and the CSV, account admins will see error messages like this:
Screen_Shot_2022-10-25_at_2.39.51_PM.png
Was this article helpful?
0 out of 1 found this helpful