You can refer to the sample data file for format recommendations, but you can import your own file. The file itself can be imported as a CVS, XLSX, or XLS. The mapping exercise for importing will guide you to how the columns in your data are assigned to SecurEnds columns.
Each application will require a unique identifier to make a match with the System of Record. This unique identifier can be either an Email or Employee ID. Without this unique identifier, SecurEnds will not make an initial match and users without unique identifier will be marked as unmatched records. Unmatched records are not reviewed when a campaign is created, therefore they would need to be matched with a user within the System of Record before initiating a review.
While importing a CSV, you will be asked which data within your app data will be used to match to the user within the People view or System of Record. You have the default option of using a First and Last Name (not full name) or an email address. The second option is by an Employee ID. Note, if matching choice is Employee ID, this must also exist in your System of Record data so it can be matched. The following bolded fields are required to be matched with columns from your imported file. If a field is not bolded below, then it that data is not required.
What happens if a record is skipped?
What if the application does not have an optional dat column such as “Employee Middle Name”?
What if the application does not contain a First Name or Last Name?
I have a batch of unmatched users and I know their unique identifier that corresponds with the SOR data. How can I quickly match these unmatched users?
Powered by BetterDocs
Other product and company names mentioned herein are the property of their respective owners.
It’s official, SecurEnds raises $21M Series A! For more details, check out our Press Release and a message from our CEO.