A Quick Start to Your First Block Restriction

Updated on February 3, 2024

What’s in This Guide

In this quick start guide, you’ll create the most basic restriction for a WordPress editor block. For this basic restriction:

  • You’ll let only logged-in visitors see a Paragraph block (default setting).
  • You’ll allow logged-in visitors to see the Paragraph block on any device (default setting).

Since you’re using all the default Content Control settings, there are only 5 steps!

Create Your First Block Restriction

1. Edit a post or page in Gutenberg (WordPress block editor)

Log into your WordPress admin and edit a post or page. Make sure your WordPress block editor is on.

2. Select a Paragraph block.

Add a new Paragraph block or click an existing one. In the screen capture below, we clicked on the paragraph block that starts with “Welcome to WordPress.”

Selecting A Paragraph Block In Gutenberg

3. Turn on Content Control for the Paragraph block.

While your paragraph is still selected, click Enable Controls under Block Controls in the block settings sidebar.

Content Control V2 Block Controls

If you don’t see the Block Controls settings right away, check that you’re in the block settings tab (gear icon).

Cc V2 Block Editor Settings Tab 297W

4. Expand User Rules

Expand the User Rules settings and keep the default settings (Logged In Users and Any).

Cc V2 Expand User Rules Demo 338W

5. Save your changes.

Click Publish or Update for your post or page, and you’re done!

Gutenberg Publish Marked 460W

Before You Go

Notice that we didn’t “touch” the Device Rules. That means we accepted the default settings (i.e., all devices). Check out How To Add a Restriction to a Block to learn more about Device Rules and User Rules.

So now, you’ll need to log in as any role to see your paragraph on any device.

Go ahead and log out. Go to your post or page. Your paragraph won’t display.

You’ll see all the other content that doesn’t have Content Control turned on.

Take it for a spin 😌

Pro tip: Always make sure to clear all caches on the browser, WordPress, server, and CDN before testing any changes.

Is this article helpful? What are your feelings