Content Restriction by User Role flags each post or page with the WordPress roles allowed to view it, storing the rule in wp_postmeta. The plugin honours role capabilities, falls back to a configurable message or redirect for unauthorised visitors, and stays close to WordPress core role semantics rather than inventing a parallel access system.

That tight integration is the strength of the plugin. It is also the reason the default admin gives no library-wide overview. Each post knows which roles can see it; the site as a whole has no screen that answers how much of the library a subscriber actually sees versus an administrator, or which roles act as the real premium tier in practice.

SleekView Charts reads wp_posts joined to the role-restriction postmeta directly. A Number anchors total role-restricted posts. A Pie splits gated content by primary allowed role. A Bar ranks roles by post count. An Area trends new role-restricted posts against publish date so editorial sees protection moving with the calendar.

Role-based content restriction is the simplest model that scales: assign content to a role, give the right users that role, let WordPress enforce the rest. The simplicity is the strength and the visibility cost. With every gating decision living in postmeta on individual posts, the editorial lead has no way to answer the basic strategic question (which role is the real premium tier on this site, and how much content sits behind it) without a spreadsheet or a custom query.

A dashboard that reads wp_posts joined to the role-restriction meta keys answers it in a glance. The per-role bar tells the team where the gating is concentrated. The over-time area tells them whether the protection cadence has slipped.

The pie tells compliance whether sensitive content really sits behind the right role. Same plugin data, one workspace.