Skip to content

Knowledgebase

Locking blocks to protect an editorial layout

wordpress

Block locking can reduce accidental movement or deletion of important layout elements while editors work on content. It is an editorial safeguard, not a replacement for WordPress user permissions or a guarantee that an authorised administrator cannot change the design.

01 Decide what should be protected

Identify stable structural blocks, such as a section container or a required introductory element. Leave the necessary content fields editable. Locking every block without a clear reason can make routine updates confusing and encourage editors to create duplicate sections instead.

02 Apply a suitable lock

  1. Open the page or template and select the intended block in List View.
  2. Open its options and choose the lock control where available.
  3. Select the restrictions needed, such as preventing movement, removal or both. For a container, review whether the lock should also apply to nested blocks.
  4. Save the change, then test the editing workflow using the role that will maintain the content.

What does a block lock actually protect?

Tell editors which content they can change and who should approve structural edits. A locked Group may still permit editing of text inside it, depending on the configuration. Content-only editing and pattern controls can impose additional constraints, so test the actual combination rather than relying on one icon.

Keep an editable staging or development copy for significant redesigns. If a layout must change, unlock the specific structure deliberately, complete the review and restore appropriate protection afterward.

03 Verify usability and troubleshoot

Check that routine tasks such as updating a link, replacing an image or correcting a heading remain possible. Review the public page after saving because locking does not fix an existing layout problem.

If an expected action disappears, inspect the selected block and its parent containers for locks. Confirm whether you are editing a pattern or template rather than ordinary page content. Do not delete a shared pattern from the library to bypass a lock on one occurrence.

If users must be prevented from making particular classes of changes for access-control reasons, review their roles and capabilities separately. The lock should make an approved workflow easier to follow, while permissions determine who is allowed to administer the site.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support