Why is an email address required for bulk import into Auth0?

[moririn]

We are trying to bulk import user information from our application’s database into Auth0’s database.

• It seems that an email address is mandatory when performing a bulk import of users, but why is that? Could you explain the reason, or point me to any official documentation that explains this requirement?
• If the email is required for user identification, is it possible to use a different field, such as userId or userName, instead of the email as the identifier?Ready to post? First, try searching for your answer.

[tyf]

Hey there @moririn welcome to the community!

An email is indeed required - This requirement is in place because the email address serves as a unique identifier within Auth0. The primary reason for this is that the email address is a globally unique identifier that can be easily used to contact the user (e.g., for password resets, multi-factor authentication, or other communications).

Importing user profiles that do not have an email attribute

Problem statement A lot of users of our app do not use email to log in and use a username instead. We want to import these users in Auth0 using a custom database with lazy migration, but Auth0 does not allow importing users with missing email IDs. The solution we are thinking of is to assign them fake email IDs. Is there any accepted pattern Auth0 suggests to assign such fake email IDs which are not routable? Solution An email field is required when importing users either through a Custom DB o…