# Pre-approving new users when local login is disabled

**URL:** <https://meta.discourse.org/t/pre-approving-new-users-when-local-login-is-disabled/126234>\
**Category:** Product Support\
**Created:** [August 19, 2019, 11:33pm UTC](https://meta.discourse.org/t/pre-approving-new-users-when-local-login-is-disabled/126234 "2019-08-19T23:33:08Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 20, 2019, 9:02pm UTC](https://meta.discourse.org/t/pre-approving-new-users-when-local-login-is-disabled/126234/5 "2019-08-20T21:02:21Z")

</div>

> [@stevewritescode](#):
>
> we want them to know they don’t need to manage another username and password.

Allowing them not to create a password and **requiring** them to let you know what email address they use with social login just isn’t the same. They can still skip having a password if they use a social login. I often refuse to sign in with my gmail account (though less frequently now) and my wife almost always refuses such. Also, the login-with-email is really handy and means that you never need a password. But I digress.

If the API requires a password, just generate a random one. Having a password that you don’t know and don’t need is pretty much the same as not having a password.

At some point I made [GitHub - pfaffman/discourse-user-creator: Create an activated user, optionally assigning to group · GitHub](https://github.com/pfaffman/discourse-user-creator); I don’t promise that it works, but it should get you pretty close. You want to create non-activated users, so you’ll need to modify it, but it should be pretty clear what to remove. (If you just want the problem solved and have a budget, please feel free to contact me.)

---

_[View the full topic](https://meta.discourse.org/t/pre-approving-new-users-when-local-login-is-disabled/126234)._