by
qaiyo
0 (0 reviews)
Qaiyo Access Manager
Control which plugins, post types and taxonomies each role or user can access, with allow/deny rules, per-user overrides and a shortcode.
Qaiyo Access Manager ranks #48,471 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Oct 13, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.4.0
Current Version v1.4.0
Updated 2 weeks ago
Last Update on 13 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#3,855 of 5,058 in Security
Downloads -26.2% this week
Actively maintained
Rank
#48,471
—
No change
Active Installs
0+
-100%
KW Avg Position
N/A
—
No change
Downloads
1.1K
+5 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
20,903
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 5 more installs to reach 10+
Rank Changes
Current
#48,471
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.4.0
- Last Updated
- Oct 13, 2026
- Requires WP
- 5.8+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- qaiyo
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about Qaiyo Access Manager
It stays accessible to everyone. Rules are opt-in: an item is only restricted once you add a rule for it.
No. Anyone with the manage_options capability always keeps full access, by design, so you can never lock yourself out.
User rules take priority over role rules. A denied user cannot access the item even if their role is allowed, and an allowed user can access it even if their role is not.
Allow mode means only the checked roles get access. Deny mode means the checked roles lose access and everyone else keeps it. Pick whichever is fewer clicks for your situation.
Use the shortcode, for example: [qaiyo_protect role="editor,shop_manager"]Visible only to these roles.[/qaiyo_protect]. Combine the attributes role (allow list), deny (deny list), logged_in (yes/no), cap (a capability) and message (text shown instead when the content is hidden).
Open the Access check tab, pick the user and the item, and read the answer. A rule here can hide or allow things, but it never grants a WordPress capability: if the user's role lacks the capability the content type or taxonomy itself asks for (for example edit_products), WordPress still blocks them, and the Access check says so. The same check is available from the command line: wp qaiyo-access explain <user> <type> <key>.
No. Every check reads your own site only (roles, users, a few settings) and the result is shown to administrators on the Capabilities tab. Nothing is transmitted, and the review does not change any role, user or setting.
No. It is a read-only inspector. Editing capabilities is intentionally out of scope so WordPress's core role system stays untouched.
Yes. CPT rules are enforced across the admin menu, list and edit queries, single front-end views (with a configurable redirect), and the core (/wp/v2/) REST API — and guests are blocked too, not just logged-in users. For content types registered with their own capabilities (most plugin CPTs, e.g. WooCommerce Products), the rules are additionally enforced at the WordPress capability level, which also covers custom REST controllers. Content types that share the generic post/page capabilities are enforced through the menu, query, front-end and core REST layers rather than at the capability level, to avoid affecting unrelated content.
Everything a user needs to manage that taxonomy in the dashboard: its menu item and screens (also via direct URL), creating, editing and deleting terms, and assigning terms to posts in the block editor, the classic editor and Quick Edit. Writes through the core REST API and admin-ajax are blocked too. Reading terms and front-end archives stay public. Shared capabilities like manage_categories are deliberately left untouched, so restricting categories never breaks tags or post editing. To hide or lock a single category or tag instead of a whole taxonomy, see Qaiyo Access Manager Pro.
