

Add New Access Rule
Permarix Content Access Manager gives WordPress site owners a practical way to control access to content without replacing WordPress’s normal user and authentication system. Create access rules, choose which roles are allowed to view protected content, decide what visitors see when access is denied, and customize the forms shown inside the locked-content experience.
Key features:
Permarix is focused on content access: it works with WordPress users and roles and adds a configurable layer for deciding who can see protected content and what experience other visitors receive.
The optional Permarix Pro add-on provides the visual editor, Gutenberg Locked Content block, page-builder integrations, per-content layout controls, advanced role management, notification features, and additional integrations.
Upgrade to Permarix Pro to unlock advanced management tools and visual customization:
* Per-Post Content Rules – Apply unique restriction rules to specific pages and posts.
* Visual Layout Designer – Customize the look and feel of your login and locked-content cards.
* Gutenberg Block & Page Builder Integrations – Easily insert locked content using native blocks.
* Advanced Role Editor – Create and manage custom user capabilities seamlessly.
* Automated Notifications – Get notified instantly of new user registrations pending moderation.
Create an access rule, select the roles that are allowed to view the protected content, and choose what should happen when someone does not meet the requirement. Depending on your configuration, Permarix can display a custom access-denied message or redirect the visitor.
You can use reusable rules for broader protection; advanced per-post controls are available in Permarix Pro.
When a visitor reaches protected content, Permarix can present Login, Register, and Forgot Password tabs in the locked-content card. You can control which forms are available and customize their labels and messages.
The plugin-owned source code is included in the distributed plugin package. No external build step is required to regenerate the plugin-owned assets.
The plugin does not require third-party JavaScript libraries for its admin content search controls; its plugin-owned JavaScript and CSS are shipped in the package.