by
qaiyo
1 (0 reviews)
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.
Qaiyo Access Manager ranks #67,335 among WordPress.org plugins with 1+ active installations, is #2,613 of 4,488 in the Security category, a 1/5 rating from 0 reviews, and was last updated Jun 17, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1)
v1.1.0
Current Version v1.1.0
Updated 2 months ago
Last Update on 17 Jun, 2026
Refreshed 12 hours ago
Last Refreshed on
#2,613 of 4,488 in Security
Rank
#67,335
—
No change
Active Installs
1+
—
No change
KW Avg Position
N/A
—
No change
Downloads
609
+3 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
63,297
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 9 more installs to reach 10+
Rank Changes
Current
#67,335
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
1.0
0 reviews
Overall
20%
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.1.0
- Last Updated
- Jun 17, 2026
- Requires WP
- 5.8+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- qaiyo
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- 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,752
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,007
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
#17
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
#38
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).
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.
It removes the plugin from the Plugins screen and removes and blocks its admin menu pages (including direct-URL access) for the restricted roles, which stops normal use through the dashboard. It does not rewrite that plugin's own internal capabilities or its private AJAX/REST endpoints. For a hard capability boundary around a specific plugin feature, combine plugin-level rules with the plugin's own role settings or a capability manager.
Yes. The plugin excludes the internal post types used by translation plugins and does not interfere with language-based content filtering.
By default your rules are preserved so they return if you reinstall. You can opt in (Settings → Tools) to delete all rules and settings on uninstall instead.
