# User Fields Defined still showing up in signup

**URL:** <https://meta.discourse.org/t/user-fields-defined-still-showing-up-in-signup/114837>\
**Category:** Product Support\
**Created:** [4월 12, 2019, 8:10오전 UTC](https://meta.discourse.org/t/user-fields-defined-still-showing-up-in-signup/114837 "2019-04-12T08:10:41Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [4월 15, 2019, 4:24오전 UTC](https://meta.discourse.org/t/user-fields-defined-still-showing-up-in-signup/114837/10 "2019-04-15T04:24:51Z")

</div>

It has behaved this way for as long as I can recall, I know several sites built on this behavior. Ticking required adds the red asterisk to the field and registration can’t be completed unless it’s provided.

Previously I took that unchecked box to mean ‘optional at signup’. If the behavior of that box is going to change, as I know several places where providing additional data is _optional_ and relies on those fields.

> [@tshenry](#):
>
> Unless user fields were always intended to show on the signup modal, and the setting is only to enforce that the field is filled before a user can sign up.

Yes, this, so different communities could ask for social media handles, etc. Asked, but not enforced.

---

_[View the full topic](https://meta.discourse.org/t/user-fields-defined-still-showing-up-in-signup/114837)._