I see that the API for creating and updating users has a verify_email option to omit sending the verification message on a case-by-case basis.
I’d like to do something similar, but for select applications. Can I do this using Actions? E.g. set the value of user.verify_email in a pre user registration flow?
It’s looking like I’ll need to disable the built-in Auth0 Verification Email (under Branding, for some reason), across the whole environment, and then separately implement a new service that itself sends the verification email after going to Auth0 for an email verification ticket.
I’m disappointed that I have to re-implement a feature that otherwise works well, so that I can have more control over if/how/when it’s used.
If there’s not a way to do this, I might recommend adding to the PostUserRegistrationAPI or something in Actions? I know that there’s already functionality to turn off verification when you add a user via the management api, but it would be nice if I could turn it off during an action or hook.
In actions, you can already do api.access.deny() to deny registration, so what if there was something like api.access.sendVerificationEmail(false) to prevent the email from being sent? Or the implementation details don’t matter. Just as long as there’s a way to selectively turn off sending verification emails.
(In my case, I have a separate “invitation” flow where the user has already clicked on a link from their email inbox, so I know ahead of time that their email is valid before they even sign up. I’d rather them not to have to click two links)
Thank you @lee.omara for posting this question on the community!
I am sorry about the delayed response to your inquiry.
Unfortunately, there is no option to disable the email verification on sign-up for specific applications. I would advise to post on the Feedback forum regarding implementing this feature.
As mentioned above, an alternative would be to send the email verification ticket whenever needed using the Management API. Otherwise, only MFA factors can be disabled via post-login actions depending on certain conditions.
If you have any other questions, feel free to leave a reply or post again on the community!