Dion Hulse

<p>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:</p>
<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 <span aria-hidden="true" class="wp-exclude-emoji">→</span> access is gone everywhere.</li>
</ol>
<p>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.</p>
<h4>Features</h4>
<ul>
<li><strong>Teams with roles.</strong> Each team carries a WordPress role (editor, administrator, a custom role, or none).</li>
<li><strong>Runtime capability grants.</strong> 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><strong>Multisite-native.</strong> 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><strong>Site scoping.</strong> A team can apply network-wide (including sites added later) or to a specific list of sites, each with its own role.</li>
<li><strong>Admin UI.</strong> Network Admin <span aria-hidden="true" class="wp-exclude-emoji">→</span> Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> Teams. Per-user checkboxes on the Edit User screen. Team rows with “— Team” markers on the Users list table.</li>
<li><strong>Cleans up after itself.</strong> 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>
<p>Team-derived capabilities are merged in at runtime, never written into the member user’s own meta:</p>
<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>
<p>The user’s actual <code>{prefix}capabilities</code> usermeta is never modified. That’s what makes team-based access instantly revocable.</p>
<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>
<p>Team management is restricted to super admins so a compromised single-site admin can’t grant themselves access across the network.</p>
<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.

Freemius

Jory Hogeveen

Joachim Jensen

DEV Institute

<p><strong>Restrict User Access is a fast and simple Membership Plugin for WordPress. Restrict your content in minutes, NOT hours.</strong></p>
<p>Quickly set up a paid membership site where your users can get different levels such as Platinum, Gold, or Free. Then, grant those levels when a user purchases a product in WooCommerce.</p>
<h3>👥 Unlimited Access Levels</h3>
<p>Users can have multiple levels, and you control how long memberships should last. When unauthorized users try to access restricted content, you can redirect them to another URL or display a teaser.</p>
<h3>⚡ Level Membership Automations</h3>
<p>Automatically add levels to your users based on something they do (Triggers) or something they are (Traits):</p>
<ul>
<li>User Registration</li>
<li>User Roles</li>
<li>Logged-in or Guests</li>
<li>WooCommerce Purchases</li>
<li>Easy Digital Downloads Purchases</li>
<li>BuddyPress Member Types</li>
<li>GiveWP Donations</li>
</ul>
<h3>🔒 Contextual Content Protection</h3>
<p>Prevent unauthorized users from visiting your posts, pages, or categories. You can even combine the conditions: protect all posts tagged “Premium” written by a select author.</p>
<p>The following Access Conditions are available out of the box:</p>
<ul>
<li>Posts, Pages & Custom Post Types</li>
<li>Content with Tags, Categories, or Custom Taxonomies</li>
<li>Content written by select Authors</li>
<li>Page Templates</li>
<li>Blog Page & Post Type Archives</li>
<li>Author Archives</li>
<li>Taxonomy Archives</li>
<li>Front Page, Search Results, 404 Not Found Page</li>
<li>bbPress Profiles, Forums & Topics</li>
<li>BuddyPress Profile Sections</li>
<li>Languages (Polylang, qTranslate X, TranslatePress, Transposh, Weglot, WPML)</li>
<li>Pods Pages</li>
</ul>
<p>Note that Access Conditions do not apply to content displayed in lists.</p>
<h3>✅ Grant & Deny Capabilities</h3>
<p>The easy-to-use WordPress User Manager gives you full control over the capabilities the members should or shouldn’t have. Access Level Capabilities will override the permissions set by roles or other plugins.</p>
<h3>👁️ Hide Admin Bar & Nav Menu Visibility</h3>
<p>Disable the admin bar for select levels and control what menu items members can see. You can even hide any widget area created with <a href="https://dev.institute/wordpress-sidebars/?utm_source=readme&utm_medium=referral&utm_content=section&utm_campaign=rua" rel="nofollow ugc">Content Aware Sidebars</a></p>
<h3>🤖 Restrict Content from Other Plugins</h3>
<p>Restrict User Access autodetects Custom Post Types and Taxonomies created by any plugin or theme. Built-in support for some of the most popular WordPress plugins means that you e.g. can restrict access to bbPress forums or multilingual content.</p>
<ul>
<li>bbPress</li>
<li>BuddyPress</li>
<li>Easy Digital Downloads</li>
<li>Pods</li>
<li>Polylang</li>
<li>TranslatePress</li>
<li>WooCommerce</li>
<li>Weglot</li>
<li>WPML</li>
<li>and more …</li>
</ul>
<h3>🛡️ WordPress Security Enhancements</h3>
<ul>
<li><strong>WP REST API Content Protection</strong><br />
Enforces PoLA to minimize attack surfaces and stop threat actors from harvesting your data</li>
<li><strong>How to display content in lists</strong><br />
Display excerpts only or hide content when post types are displayed in blog, archives, search results, lists, etc.</li>
</ul>
<h3>📑 Restrict Content with Shortcodes</h3>
<p>Fine-tune content visibility in your posts or pages by adding simple shortcodes:</p>
<pre><code>[restrict level="platinum"]
This content can only be seen by users with Platinum level or above.
[/restrict]

[restrict level="!platinum"]
This content can only be seen by users without Platinum level or above.
[/restrict]

[restrict role="editor,contributor" page="1"]
This content can only be seen by editors and contributors.
Other users will see content from page with ID 1.
[/restrict]

[login-form]
</code></pre>
<h3>👋 Developer-friendly API</h3>
<p>Restrict User Access makes it super easy for developers to programmatically customize WordPress access control by adding a few lines of code to theme templates.</p>
<h4>Example – Add level to current user</h4>
<pre><code>rua_get_user()->add_level($level_id);
</code></pre>
<h4>Example – Check if current user has an active level membership</h4>
<pre><code>if(rua_get_user()->has_level($level_id)) {
    //show restricted content
} else {
    //show content if unauthorized
}
</code></pre>
<p><a href="https://dev.institute/docs/restrict-user-access/developer-api/?utm_source=readme&utm_medium=referral&utm_content=section&utm_campaign=rua" rel="nofollow ugc">View full RUA PHP API documentation here.</a></p>
<h3>🎛️ Premium Add-ons for Restrict User Access</h3>
<p>Complete your WordPress membership site with these powerful extensions</p>
<ul>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=acf&utm_campaign=rua" rel="nofollow ugc">ACF Restriction</a></strong><br />
Restrict content that contain data from Advanced Custom Fields plugin</li>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=date&utm_campaign=rua" rel="nofollow ugc">Date Restriction</a></strong><br />
Restrict content based on the time it was published</li>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=metabox&utm_campaign=rua" rel="nofollow ugc">Meta Box Restriction</a></strong><br />
Restrict content that contain data from Meta Box plugin</li>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=timelock&utm_campaign=rua" rel="nofollow ugc">Timelock</a></strong><br />
Determine when to enable or disable select Access Conditions</li>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=url&utm_campaign=rua" rel="nofollow ugc">URL Restriction</a></strong><br />
Restrict content based on the WordPress URL, with wildcard support</li>
<li><strong><a href="https://dev.institute/products/category/restrict-user-access/?utm_source=readme&utm_medium=referral&utm_content=visibility&utm_campaign=rua" rel="nofollow ugc">Visibility Control</a></strong><br />
Hide content from blog, search results, archives, custom lists, WP REST API, and more</li>
</ul>


Restrict User Access – Ultimate Membership & Content Protection

Create Access Levels and restrict any post, page, category, etc. Supports bbPress, BuddyPress, WooCommerce, WPML, and more.

User Teams vs Restrict User Access – Ultimate Membership & Content Protection