Allow additional fields in sign up

[Tools]

allow additional fields in sign up so that profile not only exist out of an email.

[pford]

Hi Tools! This was possible in older sign-up/in blocks, but we’re looking to add this back to the new ones soon!

[Tools]

Hi Thanks for your reply. I need it because I need more info from the user before i grant access to my portal. So or the sign up form has more fields, or there is a solution for a sign up flow block (like a form with “next steps”). Current form solution is not enough, because it will generate a new record in one of my tables. I want to link the new additional info to an existing user record.

[Ben]

Meet the new Softr

That is what I figured. Just wanted to confirm. Hopefully Softr adds more fields to the new sign up to avoid unnecessary user onboarding steps and admin workflows, which is what all of this “new account management” should be about anyway. Thanks and admire your initiative!

[Ben]

Allow additional fields in sign up

Hi Tools! This was possible in older sign-up/in blocks, but we’re looking to add this back to the new ones soon!

Hi @pford. We’ve been attempting to switch apps over to the “New Softr”, but can’t complete migrations without additional sign up fields like legacy blocks have. As a Softr builder since 2020 and a business user for years, it would be nice to use the new email authentication, which has been needed since then. When will additional fields be added to sign up?

[Jjenglert]

We’re working on adding hidden fields to our signup pages that will go live shortly.

Also, I’d suggest coping your app and trying the new Softr before migrating as some items are different than previously and would be best for you to know ahead of time.

[Ben]

Thanks JJ. What about additional regular fields that capture essential user credentials for onboarding and user group assignment like older sign up blocks?

Meet the new Softr

Hi @Jjenglert. I like the idea of adding optional fields to sign up for capturing essential info about users, up front, like existing sign up blocks. This streamlines onboarding so users can get right to things after signing up, instead of taking another step to enter more info if it’s unecessary. With this new authentication, which is the same functionality as the sign-in-with-code block, extra sign up fields should be implemented similarly to the way conditional forms work where data from f…

[Jjenglert]

That will only come via our new “onboarding” process that we are planning to launch this quarter. No specific timeline on that at the moment. In situations where these additional fields on Signup are required (and you don’t want to use a workaround scenario) then we recommend not migrating until this new onboarding experiencing is live.

[nocoder]

This is a super exciting update we cannot wait for! I know you said this quarter but will it be a phased rollout or all together?

Is there any recommendation for those who built the system with the new Softr but need this functionality of input fields upon sign in? Can we use an old block to the new one and then switch it over once onboarding is launched?

For context, our use case is families signing up together and we want to link parents to children when they all make their accounts upon sign in.

[Jjenglert]

Hi there,

We are working on it already, so hoping for it within the next month or less.

Until then, I’d suggest using a conditional form that syncs to the user table. Then, turn on user invitations so when a new user is created, they are sent an email to sign in. That way, you can collect those fields for the new user when signing up, add them to your user group, and then they can sign in via email.

[justinjtessier]

Couldn’t this result in duplicate profiles with the same email?

[artur]

Quick update on the topic…

Next week we will be able to release a version where builders can add hidden fields on signup blocks…

And more powerful onboarding experience (think of multistep conditional forms) as onboarding sequence is entering into development phase next week… not yet clear how long could take but will keep posted

[nocoder]

Awesome! Super excited that will unlock the next phase of our project. Thanks team!

[Ben]

@artur

builders can add hidden fields on signup blocks…

@artur, what are the use cases for this on sign up? What would be captured and why?

[artur]

@Ben think of an app where you have different signups for teachers and students then you can send two different signup pages with some hidden values… when users created you already know one is a teacher another one is a student…

[Ben]

Thanks @Artur.
Why is this necessary though when you could send them an invitation?

[artur]

Mostly for cases when people come into a page and then do self signup I would say

[Ben]

@artur

you can send two different signup pages

Sorry @artur, it’s not clear from your responses if hidden fields are for external user, internal, or both to sign up. If external, why would you “send” this sign up? If these are internal users, why not send an invite, since hidden info would already be captured because you know who they are?

[nocoder]

Wanted to check in here - I have a demo next week for an onboarding process and need to set expectations on what will be shown… any progress on this?