Hide Content by User Role for WPBakery
View on WordPress.orgScores higher than 4% of indexed plugins
About
Hide/show/restrict elements based on user roles like administrator in WPBakery page builder (formerly Visual Composer).
What It Does
This plugin adds visibility controls to the WPBakery page builder, letting editors wrap any element in a shortcode or block-level widget that only renders for specified WordPress user roles (such as administrator, editor, subscriber, or custom roles). It provides show, hide, and restrict modes for sections, rows, and individual content blocks without writing PHP.
Who It's For
Best suited for site owners already building pages with WPBakery who need role-based content gating on marketing pages, membership landing areas, or client portals. It fits smaller agencies and course platforms that want front-end visibility rules without touching theme files or deploying a full membership plugin.
Who Should Skip It
Skip it if you are not using WPBakery, or if your gating needs extend beyond simple page elements to full post, taxonomy, or URL-level restrictions, in which case a dedicated membership plugin will serve you far better. Anyone running modern block-editor-only sites will get no value from this extension.
The Bottom Line
A narrowly focused, WPBakery-only utility that does one job and does it well enough for small sites, scoring 55.09 overall mostly because of its small install base and untested support channel. It is a sensible pick for WPBakery shops that need lightweight role gating, but anyone needing serious membership features should look elsewhere.
Related Plugins
Pick Post Duplicator when your real need is cloning posts or pages quickly, with no role-based visibility requirements.
Choose Post Type Switcher if you need to reassign content between post types instead of hiding elements based on visitor roles.
Reach for Header and Footer Scripts when your task is injecting analytics or custom code site-wide rather than gating visible content.
Use Page Links To if redirecting a page URL to another location is the simpler answer to your access problem.
Pick the Email Encoder bundle when protecting email addresses from scrapers is the goal, not restricting content per role.