Thanks - the perspective helps me understand where our assumptions were wrong. The users we are importing are considered new (by us) - not the quite the migration use case that you have documented (where you are “creating” existing users with passwords they already know). Enhancement request: Let me import users that go through the registration process so I can control what happens after import.
Follow up question: the link you cited shows a programmatic solution (calling the Management API) for creating new users. Is the only non-programming approach that triggers the Post-User-Registration action the create user on the dashboard? (I’m assuming that’s the case.)
We’re using Scroll Viewport to publish a web site from data in Confluence Cloud. The resulting web site is basically just HTML. We expected to maintain users directly through the dashboard for a while (our volumes of users in/out is not very high yet), but we thought we would import the first several hundred to save some time and effort.
I know we could create the users, and send them an email (not from Auth0) that invites them to the site and tells them not to log in but to request a change password and follow the instructions. But I was hoping we could avoid the awkward part of that process. While I found an example that used the post-user-registration action to generate the change password upon registration and morph the change password email into an invitation, I haven’t found many other ways to load bulk users and invite them to the app without writing a program. Any approaches I missed that don’t require a program on our end?
Otherwise, I’ll concede to writing a program using the Management API for our initial conversion.