Content Restriction Module Documentation

📝 Note: The Content Restriction module is part of Neve Pro, which you can get from here. If you would like to learn more about the Neve Pro Addon, take a look at Neve Pro Addon's full documentation.

The Content Restriction module allows you to restrict several content types across your website based on users, user roles, or passwords.

🖲️ Activating the Module

Install the Neve PRO using these instructions.
Navigate to  Neve > Neve Options > Neve Pro.
Scroll down and enable the Content Restriction module .

This module has three restriction behaviors: Show 404 page, Show default WordPress login page, or Show custom login page, and it can restrict the following content types: Posts, Pages, Post Categories, Product Categories (when WooCommerce is installed), and Custom Post Types.

🧰 Using the module


First, navigate to Neve > Neve PRO.


Scroll down and expand the Content restriction accordion.


Start enabling the content types for which restrictions should be added.


Under the More settings section, select the desired behavior for the logged-out users.

The module can be used to add restrictions to the following content types:

  • Posts
  • Pages
  • Categories - represents the post categories.
  • Product Categories - available if the WooCommerce plugin is installed.

After adding restrictions, you can also configure the behavior that the logged-out users will encounter on the restricted pages:

  • Show 404 page - user will be redirected to the default WP page.

  • Show default WP login page - the user will be redirected to the login form.

  • Show custom login page - for which you will have to build and select the desired login page. 

Other than these, depending on the restricted areas, you can insert the following restrictions:

  • Allow User Roles - select the roles that are allowed to access content, like author, editor, subscriber, etc.
  • Allow Users - here, you can insert the users of your website that can access the content. They can be configured in WP Dashboard > Users.
  • Password - if this is enabled, the users will be redirected to the page protected by a password. After inserting it, they will get access to the content.

🗂 Use Cases

Restricted Posts/Pages

In the following example, we have enabled restrictions for Posts and opened one of them. It works the same for Pages too.


Enable the Posts toggle to activate post restrictions.


Inside More settings, select the desired behavior for logged-out users (e.g. Show default WordPress login page).


Navigate to Posts and open the editor.


Configure the desired user roles (e.g. editor, administrator) and/or allowed users (names of the other users).


If you want to allow them access to the post, introduce a password.

📝 Note: If a post has categories (one or multiple), there will be a priority established for the restrictions: post's restrictions (if there are) > post categories restrictions > parent category of post categories. In the case of multiple parent categories, restrictions are merged. 


Restricted Categories/Product Categories

In this example, we have used the Categories toggle, which allows us to restrict post categories. It works in the same way for Product categories.


Inside the Content Restriction accordion, enable the Categories toggle.


Select the desired behavior for the logged-out users (e.g. Show 404 page).


Navigate to Posts > Categories and fill in the details of the restricted category (e.g. restrict access to anyone but Subscriber).


Under the Content restriction section, insert the allowed users, allowed user roles, and/or a password. In this example, we didn't pick a password.


📝 Note: Because we didn't use the password restriction and picked the Show 404 page, there is no way to access the Trends category.

📝 Note: If a post category has ancestors, there will be a priority applied for the restrictions: category's restrictions (if there are) > parent category restrictions. In the case of multiple parent categories, restrictions are merged. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us