Luis Rodrigues

If you have a private network where all sites are open to anyone with an account, but still want the ability to invite someone from outside and limit their access to a single site, then Network Restricted Members is for you.
This plugin was developed for our private <a href="http://p2theme.com" rel="nofollow ugc">P2</a> network, which is open to all company employees. However, we still wanted to be able to bring contractors and clients over without giving them access to everything on the network.
<h4>Usage</h4>
Network Restricted Members provides a user setting that allows multisite network administrators to restrict a user to the sites he or she is a member of.
<ol>
<li>As a super admin, navigate to the Users dashboard</li>
<li>Click ‘Edit’ on the user you wish to restrict</li>
<li>Check the option ‘Restrict User Access’</li>
<li>Save your changes</li>
</ol>
From this point on, administrators will need to add this user to their sites before he or she is able to see them.
If you wish to lift the restrictions on a user, repeat the steps above but uncheck the option box instead.
<h4>Other plugins</h4>
Network Restricted Members works best when combined with a network privacy plugin, such as one of the following:
<ul>
<li><a href="https://wordpress.org/plugins/more-privacy-options/" rel="ugc">More Privacy Options</a> by David Sader</li>
<li><a href="https://wordpress.org/plugins/network-privacy/" rel="ugc">Network Privacy</a> by Ron Rennick</li>
</ul>

Network Restricted Members

Restrict user access to selected sites on open multisite networks.

Konstantin Obenland

This plugin lets you approve or reject user registrations. 
While a user is unapproved, they can’t access the WordPress Admin.
On activation of the plugin, all existing users will automatically be flagged Approved. The site admin will never experience restricted access and does not need approval. 
This plugin is probably not compatible with WooCommerce.
<h4>Translations</h4>
I will be more than happy to update the plugin with new locales, as soon as I receive them! 
Currently available in:
<ul>
<li>Dutch</li>
<li>Deutsch</li>
<li>English</li>
<li>Hebrew</li>
<li>Persian</li>
<li>Russian</li>
</ul>
<h4>Plugin Hooks</h4>
<h3>Actions</h3>
wpau_approve (int)
<blockquote>
User-ID of approved user.
</blockquote>
wpau_unapprove (int)
<blockquote>
User-ID of unapproved user.
</blockquote>
<h3>Filter</h3>
wpau_default_options (array)
<blockquote>
Default options.
</blockquote>
wpau_update_message_handler (string)
<blockquote>
Allows to return custom update messages.
</blockquote>
wpau_message_placeholders (array)
<blockquote>
Filters the placeholders in approve/unapprove emails.
</blockquote>

WP Approve User

The plugin is not working as promised, so

1. No Settings
2. It didn't display Custom Menu for each user


Thanks, but need to uninstall.

Not Working!

This site has over 360k registered users. Upon activating the plugin, it timed out as it tried to add >720k user meta keys. Not sure why it doesn't just meta select only users who do not have the fields (which would have still timed out, but at least it would continue on the next time Activate was attempted). I "fixed" that by adding them with my own script and then uncommented the activation hook. It appeared to be working fine after that, but then I discovered (via Query Monitor) that it was adding over 6 seconds (with Redis caching!) to every admin page load because the constructor pulls a list of all unapproved users.

It would also have been nice if there was a checkbox like "Delete plugin data when uninstalled" or whatever so I didn't have to re-add over 720k meta fields to my dev box after deleting the plugin to move it as a submodule (obviously, I should have just deleted the directory, but I didn't look at the code and realize that it was going to asplode everything on my dev instance).

I get it - 360k+ users is a lot, but for plugins (plural: the others failed too, for the same reason) that assume a site is soliciting registrations from anon, you'd expect them to handle a lot of registrations. If you don't have many users/registrations, you don't really need a plugin to manage them, right?

I'm assuming that it loads a list of every unapproved user on every admin page load solely for the unapproved user count badge on the admin menu (I didn't look - I stopped trying to hack it and just decided to tell the users to manage it manually, which was unpopular).

+3 stars because it's free and doesn't use Freemius.

EDIT - Also, you can change the instantiation because I don't think it needs to run during cron or Ajax requests:
if( !wp_doing_cron() && !wp_doing_ajax() ) new Obenland_Wp_Approve_User();

You can probably check for is_admin() before running code in various places, too.

Does Not Scale


We are looking for a way to minimise the amount of emails which we send out to dead addresses (often Gmail) via fake bbPress signups to our forum. The first step is user approval.



Konstantin's plugin is simple and focused, with straightforward settings in a settings panel. There's no top level left column item (frankly any plugin which wants to put its settings in the main left window should require approval from the plugin moderation team, if in the plugin directory, the left top-level menu is now hopelessly cluttered on most WordPress sites). The main interface are simple text additions to the existing user table Approve | Unapprove.



Frankly user approval should be built into WordPress. But until it is, thank heavens for simple solutions. No adware, no pro version, no bloatware frills, native interface.



I like the idea of a previous reviewer to allow unapproved users to be kept in the database to prevent additional signups with the same address. We'd also like an improved workflow where no email goes out to users until admin approval, at which point the signup email would arrive.



What would happen to a new user is that s/he would be auto-logged in at the time of signup with very limited privileges until approved or unapproved but no email would be sent without approval. This would allow simple comments to be left on a weblog post or bbPress without sending out emails to dead addresses (and damaging sender reputation).



We can add these features fairly easily ourselves, but it would be great to see them in the core functionality of WP Approve User.



Thank you Konstantin for your hard work on WP Approve User and for making it free.


Nice, simple and focused

Adds action links to user table to approve or unapprove user registrations.

Network Restricted Members vs WP Approve User