digbodhi

Currently the plugin recognizes four roles, in order of seniority:
<pre><code>* Administrator - the built-in wordpress admin role
* Shop manager - the built-in woocommerce shop manager role
* Processor - a role created by this plugin that is meant to be a lesser shop manager role
* Customer - the built-in role that doesn't have access to the admin views
</code></pre>
As a result, the plugin does the following:
<pre><code>* Enables Shop manager to add and edit users of the Customer role 
* Enables Processor to add and edit users of the Customer role 
* Enables Administrator to control which wp-admin menus the Shop manager or Processor can see
</code></pre>
<h3>Install/Config</h3>
<pre><code>* Install the plugin
* Go to WooCommerce > Permissions Plus > Settings
* Select the dropdown role you wish to edit (admin is blocked for safety purpose)
* Select the menu checkboxes you wish to hide based on selected role
* Hit Save
</code></pre>

Permissions Plus

A plugin to manage access of the menus in wordpress/woocommerce admin view by role.  This also allows non-admin roles to create lesser users.

qaiyo

Qaiyo Access Manager extends WordPress’s built-in permission system. Out of the box, WordPress only lets you assign broad roles (editor, author, contributor…). This plugin lets administrators set fine-grained access rules for individual plugins and custom post types, at both the role level and the individual user level — without writing code or touching <code>functions.php</code>.
Hide WooCommerce from editors, give a single freelancer access to one custom post type, stop contributors from seeing a page builder, redirect each role to its own landing page after login, or protect a block of content on the front end with a shortcode. Administrators always keep full access and can never be locked out.
Plugin & content access
<ul>
<li>Plugin-level access control — Decide which roles can see and manage each installed plugin. The plugin is hidden from the Plugins screen, its action links are removed, and its admin menu pages are removed and blocked (including direct-URL access) for restricted roles. This governs visibility and admin access; it is not a substitute for a plugin’s own internal capability checks.</li>
<li>Custom post type access control — Restrict any custom post type (WooCommerce Products, ACF field groups, portfolios, events…) per role, across the admin menu, list/edit queries, single front-end views (with a configurable redirect) and the core REST API. Content types registered with their own capabilities are also enforced at the capability level, so guests and unauthorised roles are blocked, not just hidden.</li>
<li>Allow / Deny mode per rule — Each rule can either allow only the checked roles, or deny the checked roles and leave everyone else untouched — whichever needs fewer clicks.</li>
<li>User-level overrides — Allow or deny a specific user regardless of their role. User rules always win over role rules.</li>
<li>Access Matrix — A bird’s-eye grid of every plugin and post type against every role, so you can audit your whole site at a glance.</li>
<li>Native capability hints — Next to each plugin and post type, see which roles already hold the relevant WordPress capabilities, so your rules and core roles never silently conflict.</li>
</ul>
Roles, login & front end
<ul>
<li>Login redirect by role — Send each role to its own URL right after login.</li>
<li>Restricted content redirect — Choose where logged-in users land when they open a single item of a content type they cannot access (home, 404, login or a custom URL).</li>
<li>Frontend protection shortcode — <code>[qaiyo_protect role="editor" deny="subscriber" logged_in="yes" cap="edit_posts"]…[/qaiyo_protect]</code> shows or hides content by role, login state or capability, with an optional replacement message.</li>
<li>Customizable restricted notice — Pick the style (info / warning / error / none) and text shown to restricted users, with <code>{user_name}</code>, <code>{site_name}</code> and <code>{admin_email}</code> placeholders.</li>
</ul>
Admin experience
<ul>
<li>Capabilities inspector — A read-only, searchable capability × role matrix that flags core vs plugin capabilities. It never changes your roles — it just shows you what they already hold.</li>
<li>Dashboard summary widget — A WordPress Dashboard widget showing how many plugins and post types are restricted and how many user-level overrides are active, for an at-a-glance health check.</li>
<li>Hide the admin bar — Remove the frontend toolbar for selected roles.</li>
<li>Hide individual admin bar items — Strip specific nodes from the top toolbar per role.</li>
<li>Hide dashboard widgets — Remove dashboard widgets per role.</li>
<li>Update permissions — Let non-admin roles update plugins and/or themes without granting full administrator access (applied at runtime, fully reversible).</li>
<li>JSON import / export — Back up every rule to a JSON file, or migrate your whole configuration to another site.</li>
<li>Explore Qaiyo plugins — An in-admin overview of the Qaiyo plugin family, with a notice on your Qaiyo screens when a newer version of an installed Qaiyo plugin is available.</li>
</ul>
Built for the real world
<ul>
<li>Administrators are protected — Anyone with <code>manage_options</code> always has full access and cannot be restricted.</li>
<li>AJAX save — Rules are saved without a page reload.</li>
<li>Translation ready — Ships with 11 languages: English, Hungarian, German, French, Spanish, Japanese, Portuguese, Italian, Russian, Turkish and Polish.</li>
<li>Translation-plugin compatible — Plays nicely with WPML, Polylang and TranslatePress; internal translation post types are excluded automatically.</li>
<li>WordPress standards — Nonce verification, capability checks, sanitized input and escaped output throughout.</li>
</ul>
Looking for more? Qaiyo Access Manager Pro adds an editable click-to-toggle matrix, rule presets, user groups, bulk actions, temporary (time-limited) access, an activity log, admin page hiding, meta box control and email notifications.

Qaiyo Access Manager

Control which plugins and post types each role or user can access, with allow/deny rules, per-user overrides and a frontend shortcode.

Permissions Plus vs Qaiyo Access Manager