When defining custom profile fields there is an option to have them not mandatory at signup.
Yet, they still show up in the signup screen. This is not desirable since
I want the signup screen to be as simple as possible
it gives the impression that the custom field needs to be filled in
it gives the impression that the content of the custom field is somehow related to elegibility of membership, therefore may induce hesitation to signup.
So from an ux point of view, is it possible to have an option to have it removed from signup, yet still available as a field to enter in the profile afterwards. (Like “location” and such)
I’ll double check invites, if it isn’t the same there… it should be! Yep, it’s the same on invites, you can use .user-field-your-field-name there too.
@Kris’s custom CSS approach doesn’t do what we want here, because if you use that technique, it hides the field both on the signup form and in the profile.
My use case: we want to allow users to optionally declare their pronouns with a free-text field (because some users use unusual pronouns to refer to themselves), but a field like that is a honeypot for folks who think that “pronouns” are a political offense; new users get inspired to type something rude in the box.
We think it’s better not to show the field on signup, but to allow engaged users to set it by customizing their profile.