The Restrict Content Addon adds a Restrict content panel to the editor of every page, post, and public custom post type, so you can decide who may view each one: logged-in users, users with certain roles or access levels, or users whose custom user fields hold a certain value. This article covers the panel’s settings and what a visitor sees when access is denied. To restrict only part of a page, use shortcodes or block settings instead.
You need the Restrict Content Addon installed and active, which requires the Plus or Elite plan. To restrict by access level, create the levels first; see Managing access levels.
Restricting a page or post
The panel appears in both the block editor and the Classic editor.
- Open the page or post you want to restrict.
- In the Restrict content panel, select Users must be logged in to view this page (the label names the content type, such as post or product). This turns restriction on; the other settings apply only while it is selected.
- To narrow access further, fill in any of the optional settings:
- Required role (optional): the WordPress roles allowed to view. A user needs one of the selected roles.
- Required access level (optional): the access levels allowed to view. A user needs one of the selected levels.
- Custom user fields (optional): shown when the Custom User Fields Addon is active. Choose a field under Custom user field (optional) and enter the Field value it must hold; click + Add field to require more than one. A user must match every field.
- Update or publish the page.

When you set more than one kind of requirement, a user must meet each of them: for example, a required role and a required access level means the user needs one of the roles and one of the levels. If the user meets the requirements, the page loads normally.
What a denied visitor sees
By default, a visitor who does not meet the requirements, including any visitor who is not logged in, stays on the page and sees the Access restriction message in place of the content. Comments on the page are closed and hidden for them too. The message is set at Automator > Settings > Addons > Restrict content; see Managing access levels.
To send denied visitors somewhere else instead, such as a sales or login page:
- In the Restrict content panel, select Redirect if access is denied.
- Under Redirect to, choose Page and pick a published page or post from the list, or choose Custom URL (include http:// or https://) and enter the address.
- Update the page.
Things to know
- Administrators always see restricted content. Users who can manage the site’s options are never restricted, so test a restriction while logged in as another user or in a private browser window.
- Restrictions apply to the page or post itself. Search results and archive pages, such as the blog or a category page, are not restricted: they show a restricted post the way your theme shows any other post, which can be its excerpt or its full content.
- Deleting an access level lifts the restriction it set. A page that required only that level opens to every logged-in user who meets its other requirements.
Related: Managing access levels, Restrict Content Shortcodes, Restrict Content for Blocks, Restrict Content integration: triggers, actions, conditions and loop filters.
Comments (0)