Private Content / Restricted Content adds a meta box to each post that gates the content to logged-in users, to specific roles, or to a custom message for visitors. Behind that meta box, WordPress postmeta carries the gating rule per post. The plugin also supports a global default restriction set in WordPress options.

The default admin experience is per-post and works well for the editor in front of a single post. It does not give the content lead a way to see, across the whole site, how much of the library is gated, which role gates the most content, or which posts the team forgot to restrict during a recent editorial sprint. Those are aggregate questions and the data answers them, but the UI does not surface them.

SleekView Charts reads the WordPress posts table and the Private Content / Restricted Content meta keys directly. A Number anchors total gated posts. A Pie splits gating across logged-in, specific roles, and message-only. A Bar ranks roles by the number of posts they gate. An Area trends gated posts by publish date so the editorial lead sees coverage moving with the calendar.

Private Content / Restricted Content does the per-post gating job cleanly: editors set the rule on the post, the plugin enforces it, the visitor sees the message or the redirect. What goes unanswered is the library-wide view. A content site with thousands of posts and four or five gating roles cannot afford to answer questions like "are we still gating most premium content to the subscriber role" or "did this quarter's content drop ship gated" with a manual audit.

A dashboard built on the same wp_posts and wp_postmeta the plugin already uses turns those questions into a glance. Editorial leads run the sprint review off live numbers, compliance reviewers confirm coverage without a spreadsheet, and membership operators size the premium library against the subscriber base. Same plugin data, one workspace.