# How to make the password mandatory on invites?

**URL:** https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273
**Category:** Support
**Created:** [17 oktober 2019 om 16:38 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273 "2019-10-17T16:38:13Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Nacho\_Caballero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nacho_caballero/32/130189_2.png) [@Nacho\_Caballero](https://meta.discourse.org/u/Nacho_Caballero)
#### Post date: [17 oktober 2019 om 16:38 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/1 "2019-10-17T16:38:14Z")

</div>

I have an invite-only community and I would like the password field to be mandatory (it’s currently optional). Is this possible?

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [17 oktober 2019 om 17:19 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/2 "2019-10-17T17:19:07Z")

</div>

There is no setting that can be used to make the password field manditory when a user accepts an invite. If a user doesn’t set a password when they accept an invite, they will be logged into the site and a ‘Set password’ email will be sent to them right away.

From my point of view, being forced to set a password when accepting an invite would be a more straightforward user experience.

---

<div class="post-metadata">

### Author: ![Nacho\_Caballero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nacho_caballero/32/130189_2.png) [@Nacho\_Caballero](https://meta.discourse.org/u/Nacho_Caballero)
#### Post date: [17 oktober 2019 om 17:22 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/3 "2019-10-17T17:22:09Z")

</div>

I’d be happy with simply removing the word `(optional)` from the description. I assume most users know to fill it out.

I’ll use this to customize the CSS for now

```plaintext
.password-input .instructions {
    display: none;
}

```

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [17 oktober 2019 om 17:38 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/4 "2019-10-17T17:38:08Z")

</div>

You can also try customizing the `js.invites.optional_description` text. Its default value is ‘(optional)’. It is not possible to set it to an empty string, but you could set it to something like ‘in length’. That would give you the text ‘at least 10 characters in length’.

Text can be customized from your site’s Admin / Customize / Text section.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [25 juni 2023 om 03:37 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/5 "2023-06-25T03:37:22Z")

</div>



---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [25 juni 2023 om 05:09 UTC](https://meta.discourse.org/t/how-to-make-the-password-mandatory-on-invites/131273/6 "2023-06-25T05:09:51Z")

</div>

I believe the invite screen does require a password to be set now: 👍

> <https://github.com/discourse/discourse/pull/16291>
>
> Invited users were allowed to accept invites without entering a
> password. When …this happened, instead of receiving an activation email,
> they received a password reset email. Basically, a user could postpone
> choosing a password until after registration.
> 
> Unfortunately, this led to a confusing user experience and this commit
> attempts to fix that by making the client require a password. There is
> a single case when users do not need to input a password: when they sign
> up using an external authenticator and password field is completely
> hidden. In this case, the third party handles the password logic.
> 
> Technically, invites can still be redeemed without a password, but that
> functionality was kept to preserve backwards compatibility.
