Secure your content in the editor by user role with Secure Blocks for Gutenberg.

Using Secure Blocks you can add any Gutenberg block inside a secure block, have it render only to logged in users, or lock it down to a user role of your choosing.

Secure Blocks also provides an additional area that can display blocks to users that do not have permission to view the content.

For more information read the Secure Blocks introductory blog post, or view the video:

[youtube https://youtu.be/fXGPeWo_nzg]

The plugin provides the following functionality:

• Display content only to logged-users
• Display alternative content to logged-out users
• Display content to users within certain user roles
• Display alternative content to users not in those user roles

TBC

1.0.0

• First release

1.1.0

• Fixed issue whereby the plugin would not render in certain server environments

1.1.1

• Removed frontend asset enqueues that didn't do anything.

1.2.0

• Fixed issue that prevented blocks saving properly in some scenarios.

1.3.0

• Replaced withAPIData with withSelect due to depreciation in core.

1.4.0

• Updated withSelect to use latest API.

1.4.3

• Bug fixes and refactor.

1. Backup your WordPress install
2. Upload the plugin folder to the /wp-content/plugins/ directory
3. Activate the plugin through the 'Plugins' menu in WordPress

Minimum Requirements

You’ll need the Gutenberg editor active on your site.

Standard Gutenberg Content



Adding the Secure Block



What you first see when you add the Secure Block



Add any blocks to the Secure Block



Viewing the site when logged-in



Viewing the site when logged-out



Using the Inspector to select roles to lock the content down further



Locking down to certain user roles



The Secure Block interface reflects the user roles you choose



Adding content which is locked down by user role.



You are not restricted to the kind of block you can secure



A full screen image is not limited by the bounds of the Secure Block