Layout Builder Restrictions
This module grants administrative control over available blocks and layouts within Drupal's Layout Builder. It allows sites to define which blocks and layouts can be used by default, offering flexibility for usability and access control.
Summary
This module provides a configurable UI for restricting blocks and layouts. Sites can allow all options from a certain provider, or restrict all options by provider, or specify individual allowed blocks & layouts.
Drupal core will soon provide a method for controlling available blocks in Layout Builder. See #2916876: Add visibility control conditions to blocks within Layout Builder. This core solution should be sufficient for most site needs, so consider using that instead of Layout Builder Restrictions. For advanced use cases, Layout Builder Restrictions may still be useful.
Documentation
https://project.pages.drupalcode.org/layout_builder_restrictions/
Background/motivation
The default Layout Builder interface allows all blocks and layouts registered in the system. This is both a usability problem (as the list of blocks quickly becomes very large), and and access problem: some sites may not want all blocks & layouts to be available in all contexts.
Companion Modules
- Block List Override: If you want to globally suppress certain blocks from the UI on all entities implementing Layout Builder, consider using this module.
- Layout Builder Lock: limit editing actions on certain regions while allowing actions on others
- Layout Builder Restrictions by Role: control which roles can place what blocks, in all layouts.
Programmatic equivalents
To restrict blocks/layouts on all, or a group of entities, you can add your own implementation of hook_plugin_filter_TYPE__CONSUMER_alter() (which is invoked for both themes and modules). Examples are located at https://www.drupal.org/docs/contributed-modules/layout-builder-restricti....