HI @RafaPG ,
Thank you for the details.
The thing is that, the reset password is visible to non-logged-in users only. Once the user clicks on the magic link, he is already logged in, so I think the User Profile block would serve a lot for this case.
The User Profile block has a Change password feature.
I would recommend creating a page with that block and in case you add a next page parameter to the magic link to redirecting to the page with a User Profile block, you will be able to achieve what you’re looking for.
Hi Victoria. Sounds like a great idea! What about the “Old Password” field on the User Profile block? It could be a confusing journey for new users attempting to enter a new password since it can’t be removed.
@Ben Could you please elaborate more on what you mean by saying that “the user profile block doesn’t account for this scenario”? Do you mean for the scenario when a magic link gets generated?
How exactly would you like to see the user profile improvements? Those details would help us understand your use-case and consider it for future changes.
Instead of deactivated, it should be removed in this scenario since the new user hasn’t entered an initial password yet. They haven’t had the chance to submit an “Old” password yet, since they didn’t access the app using a sign up block.
@Ben let me clarify to avoid misunderstanding.
The non-logged-in user can’t access User Profile block, since it can be visible to logged-in users only.
When a magic link is generated and a user access the app via magic link, they can proceed to the User Profile block and the Old password won’t be required, but the new one can be generated. Once they change the pass, log out, when singing in, they can use the new password they have submitted in the User Profile block.
It was decided to deactivate the old password (meaning show it but making non-tapeable) and not removing it for those cases for some technical reasons, but overall the functionality is the same as if the field was removed.
Thanks for elaborating Viktoria. I was confused about what you said above earlier, but your last response is what I noticed as well. Although the functionality is the same, from a UI/UX perspective new users who are entering a password for the first time will be confused if they see an “Old password” field, regardless if it works or not.
Therefore, to avoid new user confusion leave the “Old password” field as the default in the studio for changing existing passwords, but simply provide an option to remove it for scenarios where users may be entering a new password for the first time.
I have had a similar problem whereby users can create an account however if they use one of our tools we automatically create an account for them using airtable.
Unfortunately Softr support have been extremely unsupportive on this issue.
The way i have worked around it is:
We do not use magic link
We create the account
We send an email prompting the user to reset their password to access the outputs from the tool
It is also not possible to re-trigger a password from the backend and the only work around for this is to “Re send invite” from the user panel.
My clients told me they were unable to change their password when they logged in from the magic link. I now direct them click the link and have a look around, log out and click “Forgot Password” for a temporary password to be sent to them, then to log back in and change their password. It would be much easier if the magic link prompted them to create a password in the first place.