Dion Hulse

On a large multisite network, granting a group of people the same role across many sites usually means adding each user to each site by hand — and remembering to remove them everywhere when they leave. User Teams turns that into:
<ol>
<li>Create a team, pick a role.</li>
<li>Add the user to the team.</li>
<li>They have that role everywhere the team applies.</li>
<li>Remove them from the team → access is gone everywhere.</li>
</ol>
User Teams is multisite-only by design — on a single-site install, native WordPress roles and capabilities already cover the whole feature set, so WordPress won’t offer it for activation there.
<h4>Features</h4>
<ul>
<li>Teams with roles. Each team carries a WordPress role (editor, administrator, a custom role, or none).</li>
<li>Runtime capability grants. Team access is added via the <code>user_has_cap</code> filter, so removing a user from a team drops their access on the next request — no stale capabilities usermeta to clean up.</li>
<li>Multisite-native. Team definitions are real <code>wp_users</code> rows (“team accounts”), so <code>WP_Users_List_Table</code>, <code>is_user_member_of_blog()</code>, and every column-adding plugin “just work”.</li>
<li>Site scoping. A team can apply network-wide (including sites added later) or to a specific list of sites, each with its own role.</li>
<li>Admin UI. Network Admin → Users → Teams. Per-user checkboxes on the Edit User screen. Team rows with “— Team” markers on the Users list table.</li>
<li>Cleans up after itself. Deleting a team removes its memberships. Deleting a user drops their memberships. Deleting a site removes its grants from any team that targeted it.</li>
</ul>
<h4>How access is granted</h4>
Team-derived capabilities are merged in at runtime, never written into the member user’s own meta:
<ul>
<li><code>user_has_cap</code> — adds the team role’s capabilities to the user’s effective caps, plus <code>role-{slug}</code> for plugins that check by role.</li>
<li><code>get_blogs_of_user</code> — adds team-linked sites to the user’s “My Sites” navigation.</li>
<li><code>get_user_metadata</code> — returns an empty-array <code>{prefix}{blog_id}_capabilities</code> for team members so <code>is_user_member_of_blog()</code> returns true without stamping real capabilities on the user. Workaround for <a href="https://core.trac.wordpress.org/ticket/65096" rel="nofollow ugc">Core #65096</a>.</li>
</ul>
The user’s actual <code>{prefix}capabilities</code> usermeta is never modified. That’s what makes team-based access instantly revocable.
<h4>Capability requirements</h4>
<ul>
<li>Managing teams (create / edit / delete) requires <code>manage_network_users</code> — super admin only.</li>
<li>Attaching an existing team to the current site uses <code>promote_users</code>, the same cap as inviting an individual user there.</li>
</ul>
Team management is restricted to super admins so a compromised single-site admin can’t grant themselves access across the network.
<h4>Extension filters</h4>
<ul>
<li><code>user_teams_team_caps_for_user( $caps, $user_id, $blog_id )</code> — modify the capability map computed from a user’s teams.</li>
<li><code>user_teams_team_applies_to_site( $applies, $team_id, $blog_id, $team )</code> — gate coverage (e.g. pause a team during a freeze).</li>
<li><code>user_teams_team_save_data( $data, $team_id_or_null, $op )</code> — filter sanitised input on create/update.</li>
</ul>

User Teams

Unix-style user groups for WordPress multisite. Create a team, give it a role, drop users in — access lights up across the network.

Airton Vancin Junior

This plugin gives administrators fine-grained control over content visibility in the WordPress admin area. Instead of a one-size-fits-all approach, you can set specific viewing permissions for each user role.
Core Features:
<ul>
<li>Role-Based Permissions: For each user role (like Editor, Author, Contributor), you can decide what content they are allowed to see.</li>
<li>Flexible Rules: Choose between two simple but powerful rules for each role:
<ul>
<li>See only their own content: The user will only see the posts, pages, or custom post types they have personally created.</li>
<li>See all content: The user will have no content restrictions and can see everything, just like an administrator.</li>
</ul>
</li>
<li>Admin Bar Cleanup: The “Edit” link on the admin bar is automatically hidden when a user is viewing a post they don’t have permission to see.</li>
<li>Administrator Override: Administrators are never affected by these rules and can always see all content.</li>
</ul>
This is the perfect tool for multi-author websites, magazines, or any project where you need to ensure users only have access to the content relevant to them.
<h3>License</h3>
This file is part of Manage User Roles.
Manage User Roles is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published 
by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Manage User Roles is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of 
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Get a copy of the GNU General Public License in <a href="http://www.gnu.org/licenses/" rel="nofollow ugc">http://www.gnu.org/licenses/</a>.

Manage User Roles


This 'Manage User Roles' plugin is an absolute game-changer for anyone running a WordPress site! It provides an incredibly intuitive and powerful interface for customizing user roles and capabilities. I was able to set up granular permissions in minutes, which has significantly streamlined my workflow and improved site security. The plugin is well-designed, easy to navigate, and performs flawlessly. A must-have for any serious WordPress administrator!


Essential Plugin for Granular User Role Control

A flexible plugin to control content visibility for non-administrator users with advanced, role-based rules.

User Teams vs Manage User Roles