bobbyalcorn

Restrictly™ delivers professional-grade access control without compromising your site’s speed or reliability. 
It enforces rule-based visibility across pages, posts, menus, Full Site Editing (FSE) blocks, search results, and REST API responses, while maintaining full compatibility with themes and page builders.
In the free version, access rules are driven by user roles and login status, providing a clean and reliable foundation for content and navigation control.
Includes Extended Visibility Filtering, which automatically hides restricted content from search results, archives, and public listings.
For full documentation, setup guides, and developer notes, visit the <a href="https://restrictlypro.com" rel="nofollow ugc">official Restrictly™ website</a>.
<h3>Features</h3>
<ul>
<li>Full Site Editing (FSE) Integration – Add block-level visibility directly inside the Site Editor. 
Choose who can see each block (Everyone, Logged-In, Logged-Out, or Specific Roles) with optional color-coded indicators.</li>
<li>Navigation Block Support (FSE Menus) – Manage visibility for navigation links, submenus, and page lists directly within the Site Editor.</li>
<li>Extended Visibility Filtering – Automatically hides restricted content from:
<ul>
<li>Search results</li>
<li>Category, tag, and author archives</li>
<li>Home listings and custom queries</li>
</ul>
</li>
<li>REST API Enforcement – Applies Restrictly™ visibility rules to REST API responses, automatically filtering restricted content for unauthorized users.</li>
<li>Dynamic Menu Visibility (Classic Menus) – Control menu item visibility by login state or user role in the classic menu editor.</li>
<li>Full, Quick, and Bulk Edit Support – Manage restrictions from any editor interface.</li>
<li>Sortable, Filterable Columns – Instantly see and organize restricted items in list tables.</li>
<li>Administrator Override – Allows administrators to bypass restrictions for testing.</li>
<li>Divi & Page Builder Compatibility – Works perfectly with Divi and other builders.</li>
<li>Performance-Focused & Secure – Built entirely on WordPress core APIs with strict sanitization and escaping.</li>
<li>Translation Ready – Includes a <code>.pot</code> file for localization.</li>
<li>Clean Uninstall – Removes all plugin data and options when uninstalled.</li>
</ul>
<h3>Usage</h3>
<h4>Restricting Content</h4>
Restrictly™ lets you limit access to any page or post using intuitive controls: 
– Login-Based Restrictions – Limit visibility to Logged-In or Logged-Out users. 
– Role-Based Restrictions – Allow access only to specific user roles. 
– Enforcement Actions – Display a custom message or redirect unauthorized users. 
– Administrator Override – Admins can always access restricted content when enabled.
<h4>Restricting Blocks (FSE)</h4>
Restrictly™ integrates directly with the WordPress Site Editor (FSE) to provide per-block visibility: 
– Choose Everyone, Logged-In, Logged-Out, or Specific Roles. 
– Instantly preview restrictions using colored visibility indicators. 
– Restrictions are enforced server-side for full security and consistency.
<h4>Restricting Navigation (FSE Menus)</h4>
Restrictly™ also controls FSE Navigation menu visibility: 
– Show or hide individual links, submenus, and page lists by login status or role. 
– Works natively inside the block-based Navigation editor.
<h4>REST API Enforcement</h4>
Restrictly™ applies identical access logic to REST API endpoints. 
Unauthorized users see redacted content instead of restricted data — ensuring privacy across your site.
<h4>Search & Archive Filtering</h4>
Restricted content is automatically excluded from: 
– Search results 
– Category, Tag, and Author archives 
– Home and custom queries
<h4>Restricting Menu Items (Classic Menus)</h4>
<ul>
<li>Login-Based Visibility – Show menu items only to Logged-In or Logged-Out users.</li>
<li>Role-Based Visibility – Display menu items only to selected roles.</li>
<li>Conflict Detection – Highlights mismatched menu vs. page restrictions for easy correction.</li>
</ul>
<h3>Privacy</h3>
Restrictly™ does not collect user data, track activity, or transmit information externally.
<h3>Contributing & Support</h3>
Development happens on GitHub — pull requests and issue reports welcome: 
https://github.com/bobbyalcorn/restrictly
For full documentation and support, visit: 
https://restrictlypro.com

Restrictly – Access Control

Performance-focused access control for WordPress, enforcing rule-based visibility across content, menus, and blocks with a clean core.

meceware

<a href="https://www.meceware.com/docs/block-permissions-for-gutenberg/" rel="nofollow ugc">Full Documentation</a>
<h3>How To Use</h3>
<ul>
<li>Activate ‘Block Permissions’ plugin.</li>
<li>Edit any page with Gutenberg editor.</li>
<li>If Block Permission is chosen for ‘Show’, the block content will be shown if the settings are validated. Otherwise block content will be hidden.</li>
</ul>
<h4>Show</h4>
<ul>
<li>
If ‘Everyone’ is selected as the permission, the block content will be shown for everyone.
</li>
<li>
If ‘Members’ is selected as the permission, the block content will be shown for the logged in users.
</li>
<li>
If ‘Members with Selected User Roles’ is selected as the permission, the block content will be shown only for the members with specified user roles.
</li>
<li>
If ‘Selected Users’ is selected as the permission, the block content will be shown only to the specified users.
</li>
<li>
If ‘Selected Devices’ is selected as the permission, the block content will be shown for the specified devices, such as Desktops, Phones and/or Tablets.
</li>
<li>
If ‘Date Range’ is selected as the permission, the block content will be shown between the specified dates.
</li>
<li>
If ‘Time Range’ is selected as the permission, the block content will be shown between the specified times.
</li>
<li>
If ‘Day Of Week’ is selected as the permission, the block content will be shown on the specified days.
</li>
<li>
If ‘PHP Function’ is selected as the permission, the block content will be shown according to the return value of the specified PHP function.
</li>
</ul>
<h4>Hide</h4>
<ul>
<li>
If ‘Everyone’ is selected as the permission, the block content will be hidden from everyone.
</li>
<li>
If ‘Members’ is selected as the permission, the block content will be hidden from the logged in users.
</li>
<li>
If ‘Members with Selected User Roles’ is selected as the permission, the block content will be hidden from the members with specified user roles.
</li>
<li>
If ‘Selected Users’ is selected as the permission, the block content will be hidden from the specified users.
</li>
<li>
If ‘Selected Devices’ is selected as the permission, the block content will be hidden from the specified devices, such as Desktops, Phones and/or Tablets.
</li>
<li>
If ‘Date Range’ is selected as the permission, the block content will be hidden between the specified dates.
</li>
<li>
If ‘Time Range’ is selected as the permission, the block content will be hidden between the specified times.
</li>
<li>
If ‘Day Of Week’ is selected as the permission, the block content will be hidden on the specified days.
</li>
<li>
If ‘PHP Function’ is selected as the permission, the block content will be hidden according to the return value of the specified PHP function.
</li>
</ul>

Block Permissions

Show Gutenberg editor blocks only to target audience depending on their user attributes such as user role, log in information and user names.

Restrictly – Access Control vs Block Permissions