WordPress plugin · v0.1.0
Rootstuff Block Permissions.
Hide blocks and patterns from the WordPress editor by user role and post type. Built for agencies handing sites off to clients.
01 / The problem
The editor is powerful. That is the problem.
You build a careful site and hand it to the client. Within a week, someone has dropped a Code block into a landing page and the layout has gone with it. The story is familiar.
Most block manager plugins hide blocks globally. That holds until an Editor needs the Cover block on Posts while a Contributor shouldn't have it on Pages. Then the choice is custom PHP or compromise.
Rootstuff Block Permissions resolves this with a simple settings screen. Pick a role, pick a post type, tick the blocks to hide. Every rule is scoped, every override is predictable, and the whole configuration lives in a single WordPress option.
Users with multiple roles get the least restrictive result across their roles, so no one is accidentally locked out. And because it's a denylist, new blocks added by plugin or theme updates remain available until you explicitly hide them.
No code. No external connections. No analytics. A clean interface for the one thing agencies keep solving by hand.
02 / Features
One plugin, total block control.
Most block managers are global. This one scopes every rule by role and post type, because that is what agencies actually need.
Per-role, per-post-type rules
Editors get one toolkit on Pages, another on Posts. Contributors get locked down further. As granular as the site requires.
Blocks and patterns
Hide any registered block or pattern from the inserter. Core, theme, plugin, ACF blocks: if it's registered, it appears in settings.
Denylist mental model
An empty list means nothing is blocked. Tick what should be hidden. New blocks added later are automatically allowed until you say otherwise.
Smart override matching
Rules resolve most-specific-first. Exact role plus post type beats role-only, which beats post-type-only, which beats the default. Predictable every time.
Administrator preview toggle
Admins bypass restrictions by default. Flip the toggle to preview the client experience without switching accounts.
Zero performance overhead
Reads a single option, computes a denylist, hands it to WordPress. No database query per block, no remote calls, no bundled libraries.
03 / Questions
Does it work with ACF blocks, theme blocks, and plugin blocks?
Yes. Anything registered through register_block_type() shows up automatically. ACF blocks register on acf/init, which runs before the settings page renders, so they're picked up too.
Will it affect what visitors see on the front end?
No. The plugin filters the block editor's inserter only. Existing content is never modified. Pages built before you add a rule keep working exactly as they did.
Will it slow down the editor?
No. The plugin reads a single option, computes a denylist for the current user, and hands the filtered list to WordPress. There's no database query per block, no remote calls, and no bundled libraries beyond what WordPress already loads.
How is this different from other block manager plugins?
Most block managers are global: one allowlist for everyone. Rootstuff Block Permissions scopes every rule by user role and post type, so you can give different toolkits to different roles on different content types. That's the use case agencies actually face.
What happens if I deactivate or delete the plugin?
Deactivating leaves the settings in the database so reactivating restores your rules. Deleting via the WordPress Plugins screen removes the option entirely. Either way, no content is ever modified.
Does it work with multisite?
The plugin runs per-site. Settings are stored per-site. Network-level configuration is not currently supported, but it is on the radar.
04 / Get started
Installed in under a minute.
Free on the WordPress plugin directory. Activate, tick what should be hidden, and hand the site over with confidence.
Download on WordPress.org →