Conditional user signup form

Feature Requests
1

For our set up we request a lot of optional information from our end users.
I was wondering if it would be possible to add the awesomeness that is conditional forms and the user account block together?

2 Likes
2

+1

1 Like
3

Noted and shared with team!

4

+1… This would be very useful for our use case

5

+1

6

+10!

7

+1. We have different T’s and C’s for different user sign ups

8

We are following this, but cannot commit to any kind of deadline at the moment.

Until then, we suggest you create create another table for “onboarding” and after sign up, send users to a form that creates a new entry in that table using the user as the relationship. You can even use automations after the fact to transfer that data back to the user table if you prefer to hold it there.

9

Just curious. What are the use cases for this? Internal tools and client apps, and/or something else?

10

I think users are just looking for a more flexible way to collect information on signup from their users @Ben and it applies to all types of applications.

11

Hi all, we’re currently revamping how user management in Softr works overall along with new user-related blocks.

In a nutshell: Everything around login, sign-up, and authentication will be a lot smarter and follow modern standards in terms of UX & security — with minimal effort from your end.

After that, we are planning on letting you create an "onboarding flow" for your users (invited or self-sign up) where you can require them to enter some profile info, agree to certain documents, or wait for approval form your end.

But as JJ mentioned, you can already do this today by creating an “onboarding incomplete” user group (condition-based) and updating user records once they’ve gone through it!

However, we don’t yet have a plan to offer this pre-signup because:

  • The outcome seems to be the same as requiring them to enter these info post-signups.
  • From UX + business perspective, it’s also better that they first create an account → and then complete these extra steps, especially when the extra steps required are rather long. If they drop off before signing up, you’d have no way of following up, and all their progress will be lost → Making them less likely to come back.
  • If it’s simply about routing them to the correct signup form based on some questions, you can already do that today with our new “conditional form ending” feature (announcement coming soon ;))

But if you have any strong reason why it has to happen pre-signup, we’d love to hear it and will definitely take it into consideration.

1 Like
12

Thanks for the update @austinyang. The security improvement sounds great, since this has been a longstanding issue. Also, the “onboarding flow” makes sense, depending on the use case. As for what JJ mentioned, it’s unnecessarily complicated and costly to configure in our databases and with 3rd party integrators, and can create a redundant onboarding UX when they have to sign up, then fill out more forms post-sign up.

Whatever is proposed, what’s deployed should be in consideration for internal, client, and self sign up. Sign up blocks need email validation, similar to the functionality of the ‘Sign In With Code’ block. Also, if the onboarding flow will depend on our database approval, I propose that self sign up users without approval be removed from the Softr Users table automatically. Builders will have captured them in their databases and concluded that there is no need for them as a logged in Softr user at that point.

So a good start for self sign up would involve adding email validation to sign up blocks and a FLEXIBLE “two-way” user sync where users deleted in databases are then deleted in Softr’s users tables.

If deployed something like this, builders will have more power in deciding who they want accessing their apps and get the value they are paying for per approved user in their Softr Users Tables.

1 Like