Qaiyo Access Manager
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, custom post types and taxonomies , at both the role le
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, custom post types and taxonomies , at both the role level and the individual user level — without writing code or touching functions.php .
Hide WooCommerce from editors, give a single freelancer access to one custom post type, keep authors away from your category structure, 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
- 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.
- 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.
- Taxonomy access control — Decide which roles or users may manage each taxonomy (categories, tags, product categories, custom taxonomies): its admin screens, and creating, editing, deleting and assigning its terms. Restricted users lose the taxonomy’s menu item, its screens (including direct URLs), its panel in the block and classic editors and in Quick Edit, and write access through the REST API and admin-ajax. Shared WordPress capabilities such as manage_categories and edit_posts are never changed, so other taxonomies and post editing keep working. Front-end term archives are not affected.
- 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.
