# No approve button for new user

**URL:** <https://meta.discourse.org/t/no-approve-button-for-new-user/125725>\
**Category:** WordPress\
**Created:** [13 augustus 2019 om 22:50 UTC](https://meta.discourse.org/t/no-approve-button-for-new-user/125725 "2019-08-13T22:50:47Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![markwill](https://avatars.discourse-cdn.com/v4/letter/m/90db22/32.png) [@markwill](https://meta.discourse.org/u/markwill)\
**Post date:** [15 augustus 2019 om 13:39 UTC](https://meta.discourse.org/t/no-approve-button-for-new-user/125725/8 "2019-08-15T13:39:29Z")

</div>

Although we have the weirdness with having to both activate AND approve **some** users after they try to log on. it does seem to be working. With the settings we have, the admin has to approve requests after each user tries to log for the first time. That is fine (kinda - see below), so the two settings (use SSO and approve users) seems to be OK.

That said, the inability to pre-approve a set of users, before the user makes that first log on attempt, is unfortunate and quite a problem. That means the user has a wait before they can log on, even though we (admins) are perfectly aware of who they are ahead of time.

I suspect @simon is correct about this being an edge case **from a Discourse perspective**. However. it’s pretty common for WooCommerce sites to sell both regular products and memberships. I am in that situation and it’s a pretty common scenario. So my users are split into two (and overlapping) logical sets - customers and members. I want to be able to pre-approve the list of members so they don’t have to wait for approval. I may look at automating this later but it will have to be after my forum launch on September 1st, which is a shame.

---

_[View the full topic](https://meta.discourse.org/t/no-approve-button-for-new-user/125725)._
