Description
The Pages by User Role for WordPress restricts the viewing of individual pages based on the user role, adding a metabox to each page editor where you choose which roles (administrator, editor, author, subscriber, or custom roles) have access to the content. It is suitable for sites with private areas, corporate intranets, and portals that need to segment institutional pages by permission level without installing a heavy membership solution.
Key Features of Pages by User Role for WordPress
- Metabox per page
Adds a side panel in the editor to select which roles can view each page. - Compatibility with custom roles
Recognizes roles created by other plugins such as User Role Editor and Members. - Automatic front-end blocking
Hides restricted pages from menus, listings, and search results for users without permission. - Granular control for logged-in users and visitors
Distinguishes treatment between anonymous visitors and authenticated users in each role. - Operation without theme changes
Works through WordPress filters and hooks, eliminating the need to edit templates or functions.php.
Benefits of Pages by User Role for WordPress
- Private areas without complexity
Creates restricted sections on the site without needing to configure a complete membership system. - Clear content segregation
Keeps internal documents and announcements separate from public content with just a few clicks. - Quick implementation
Restricts existing pages without rebuilding the site structure or migrating to another theme. - Compatibility with other tools
Works alongside role management plugins, adding to the stack without conflict.
Who Is Pages by User Role for WordPress For?
- Those who maintain corporate intranets and need to grant internal-page access only to authenticated employees.
- Designed for those who offer exclusive content to registered customers on support and documentation portals.
- Association, cooperative, and community sites that segment announcements by membership level.
- Those who use custom roles in WordPress and need to link specific pages to those roles.
How to Download Pages by User Role for WordPress
The Pages by User Role for WordPress is available for download here on Ultrapack. After saving the .zip file, install it in Plugins > Add New > Upload Plugin, select the package, and activate it. The access-control metabox will appear in each page editor immediately after activation.
On sites with an active user base, Pages by User Role for WordPress fills the gap between fully public pages and heavy membership platforms, applying reading restrictions at the role level without changing the theme. The metabox approach keeps the editorial workflow intact, and menu filters prevent users without permission from even seeing links to blocked content.
Frequently asked questions
Is Pages by User Role for WordPress GPL-licensed?
Yes. Pages by User Role for WordPress is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use Pages by User Role for WordPress on multiple sites?
Yes. You can install Pages by User Role for WordPress on as many sites as you want. Only automatic updates through Ultrapack Auto Updater have a limit: from 3 to 80 sites, depending on the plan.
How much does Pages by User Role for WordPress cost at Ultrapack?
Pages by User Role for WordPress costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does Pages by User Role for WordPress include updates?
Yes. The current version of Pages by User Role for WordPress is 1.7.2.101119, published at Ultrapack on Apr 20, 2024. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is Pages by User Role for WordPress scanned before publication?
Yes. Every version of Pages by User Role for WordPress goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin Pages by User Role for WordPress?
Requires WordPress 4.7 or higher. Tested up to WordPress 6.5.2.
What changed in this version
Version 1.7.2.101119
- New Feature: Add always Allow Usernames and always Disallow Usernames access control. Access by username has higher priority than access by user role.
Version 1.7.1.10456
- New Feature: Added support for allowing specific usernames to login. Is useful if you need to perform maintenance on your website and only want specific users to access your website (wp-admin).
Version 1.7.0.10317
- New Feature: Added an option to hide a post (custom post type) from the frontend, but continue to show in wp-admin, Ajax, and REST API. Use case: Hiding a course from the frontend of the website, but still showing the course inside the BuddyBoss App.
- New Feature: Added Integrations tab to Settings. Allows the Administrator to toggle ON/OFF the hide in frontend setting in the Access Control metabox.
- New Feature: Added status message in post list (Access Control column)
- Version: 1.6.5.100179 - October 29, 2021
- Bug Fixed: When a role is blocked from the front page, WooCommerce checkout Ajax crashes.
Version 1.6.4.99097
- New Feature: Restrict an entire Post Type by User Role. This will ignore the option to allow non-logged in users access to restricted content. If the user role has access to the post type, other restrictions may still apply. Like when individual settings are set for an individual Post Type.
Version 1.6.3.99091
- New Feature: Access to wp-admin by User Role.
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
- Download the file
codecanyon-136020-pages-by-user-role-for-wordpress-wordpress-plugin.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
codecanyon-136020-pages-by-user-role-for-wordpress-wordpress-plugin.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 4.7 or higher. Tested up to WordPress 6.5.2.
Stuck on a step? Open a ticket telling us which one you stopped at.

UAU Ready