<p>Currently it has no affect on the Lightswitch field at all, which I think is the right call.</p>

<p>However, you do have a valid use-case for either making a setting on the field that forced it to be "on" if required is set or maybe even a separate "Require On" field type all-together.</p>

<p>Regardless, probably worth putting up on <a href="http://feedback.buildwithcraft.com" rel="nofollow">http://feedback.buildwithcraft.com</a></p>

CC BY-SA 3.0
2015-09-29T21:01:21.730Z
2015-09-29T21:44:04.433Z
2015-09-29T21:44:04.433Z
Brad Bell
<p>If I set a Lightswitch field as required, does that require it to be On? Is that valid at all?</p>

<p>(Context: I'm using a Lightswitch in User fields to capture "I agree to the Terms &amp; Conditions...", and building a front-end user registration form.)</p>

<p>Thanks!</p>

<user-profile><lightswitch><required>
How does Craft regard a Lightswitch field when it's set to Required in the Fields layout?
# How does Craft regard a Lightswitch field when it's set to Required in the Fields layout?

(Asked by: username_0 on 2015-09-29)

If I set a Lightswitch field as required, does that require it to be On? Is that valid at all?

(Context: I'm using a Lightswitch in User fields to capture "I agree to the Terms & Conditions...", and building a front-end user registration form.)

Thanks!

**Tags:** user-profile, lightswitch, required

---

## 1 answers

### Answer by username_1 on 2015-09-29. Score: 6 | Accepted answer

Currently it has no affect on the Lightswitch field at all, which I think is the right call.

However, you do have a valid use-case for either making a setting on the field that forced it to be "on" if required is set or maybe even a separate "Require On" field type all-together.

Regardless, probably worth putting up on <http://feedback.buildwithcraft.com>


---

