Hey Stytch team!
Is there a way to remove the login without password button from the reset password email template? I couldn’t find anything in the docs or in the Email Customization from the dashboard.
Thanks.
Hey Stytch team!
Is there a way to remove the login without password button from the reset password email template? I couldn’t find anything in the docs or in the Email Customization from the dashboard.
Thanks.
Hey Gabriel – thanks for posting!
We don’t currently offer a way to remove the “Log in without password” button, but this is something that we’ve heard in the past and I’ll raise your request internally. As context for our team, would you be willing to share why you’re interested in removing it?
I’ll note that we do offer a premium feature (requires a contractual monthly minimum) that enables full HTML customization of all Stytch emails, which would allow you to remove the button from your templates. If this is something that you’re interested in, please let me know and I can connect you to the right person (or feel free to reach out directly here, whatever you prefer)!
Hi, has this feature to disable the login without password been built?
My use case is that I have disabled the use of magic links altogether from the authentication flow and this feature/button in the password reset email complicates the UX experience since it won’t work.
I’d like to request that feature too BECAUSE when we have a website and a native app the user is lost when the deeplinking isn’t set.
Hey Alex, thanks for posting! I’ll +1 this feature request internally on your behalf.
In case anyone else is looking on and is interested, quick update here since my original post – we now offer full HTML email template customization (which would allow you to remove this button yourself) as part of our branding package, which we currently offer for $99/ month.
I will note that the “Reset password” button and the “Log in without password” buttons essentially work the same way (redirecting the user back to your application via a Magic Link), so in most cases you should be able to support both buttons using the same strategy. I’d be curious to hear if that’s not the case in your app!