# Bug: UserField "Editable after signup" automatically forces "Show on signup"

**URL:** <https://meta.discourse.org/t/bug-userfield-editable-after-signup-automatically-forces-show-on-signup/386949>\
**Category:** Bug\
**Tags:** user-custom-fields\
**Created:** [October 28, 2025, 3:33pm UTC](https://meta.discourse.org/t/bug-userfield-editable-after-signup-automatically-forces-show-on-signup/386949 "2025-10-28T15:33:22Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)\
**Post date:** [October 28, 2025, 3:49pm UTC](https://meta.discourse.org/t/bug-userfield-editable-after-signup-automatically-forces-show-on-signup/386949/4 "2025-10-28T15:49:44Z")

</div>

> Fields that are optional but not editable need to be on the signup form, or they can never be filled in

The goal of the current implementation was to prevent admins from creating a user field that is neither editable nor shown on sign up. So if something is a bug, then it’s that you can still create the field without these properties. I would prefer if instead of fixing that, the [@team](https://meta.discourse.org/groups/team) would consider the use case of staff-only user fields and fulfill that feature request. That’s why I posted in the feature topic.

---

_[View the full topic](https://meta.discourse.org/t/bug-userfield-editable-after-signup-automatically-forces-show-on-signup/386949)._