# 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:** 2

<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:37pm UTC](https://meta.discourse.org/t/bug-userfield-editable-after-signup-automatically-forces-show-on-signup/386949/2 "2025-10-28T15:37:35Z")

</div>

I don’t think it’s a bug. It’s intended to work that way. But I agree it would be helpful if this was possible

> [@Option to include user field that is only editable by staff](https://meta.discourse.org/t/option-to-include-user-field-that-is-only-editable-by-staff/198099/14):
>
> But I think there is still a problem: you are forced to allow either editing or showing at signup.
> 
> [discourse/frontend/discourse/admin/components/admin-user-fields-form.gjs at d82dc69d1d4cbf7dd5ed449ae299908282637b3f · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/d82dc69d1d4cbf7dd5ed449ae299908282637b3f/frontend/discourse/admin/components/admin-user-fields-form.gjs#L64-L71)
> 
> ```plaintext
> @action
> setEditable(value, { set }) {
> set("editable", value);
> 
> if (value === false) {
> set("show_on_signup", true);
> }
> }
> 
> ```
> 
> It is possible to create a field with all options disabled because you don’t need to change the editable setting for that. But once you change it once, there is no way back to this configuration.
> 
> Based on the pull request [FEATURE: Allow hiding user fields on signup form by Drenmi · Pull Request #34672 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/34672) this was an intentional decision:
> 
> > Fields that are optional but not editable need to be on the signup form, or they can never be filled in
> 
> I wonder if the use case to have the field filled by staff was not taken into account

---

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