User signup flow - still not solved?

I know the question has been asked, but still doesn’t seem to be solved. It’s the signup flow, with magic links!

Here’s the setup for our onboarding:

  1. We send out a magic link to our costumer.
  2. With this link they land on a softr page with a user account, where I hide the “type in the old password” with a script.
  3. After setting their password, I redirect them to the main page.

The problem occurs when users log out and log back in: they are directed back to the password change page instead of the main page. This happens because the redirect page is set for “after signup,” and the logic is not distinguishing between first-time signup and regular logins.

Has anyone encountered this issue? How do you manage the redirect flow to ensure users don’t get stuck on the password change page after their initial signup?

I am using a scenario like this, and my users are at least not confused:

  1. send out a magic link
  2. for logged-in users in their user account, I don’t integrate the “change password” block.
  3. when a user logged out and want’s to log back in, he lands (for the first time) on the sign-in page where I write; “create a new password” instead of forgot password.
  4. I keep this terminology for the entire process, so looks like, the user just creates a new password, instead of “he forgot the password”.

would be happy for a better solution, but didn’t find one…

The way I did it is that once the user creates a password, they are forwarded to the “forgot password” block but I renamed it to “set new password” to avoid confusion. The users then can use their Emails to create a new password for their account. Definitely not the most convenient but I think it is better than updating it from their user profile block after logging in.

From the link thread you’ll see that Softr has no native solution. You have to use 3rd party integrators, manipulate inappropriate blocks with custom code that can break, or create a redundant new password creation journey. Softr is not interested in making it easier for onboarding users securely, especially external, otherwise they would have deployed this along with email verification already.