Private Content / Restricted Content adds a meta box to each post that gates content to logged-in users, to specific roles or to a custom message for visitors. The rule lives in wp_postmeta per post, the plugin honours WordPress role capabilities and a global default restriction set lives in wp_options. The per-post editing experience is clean.

The aggregate experience is not. With thousands of posts and four or five gating roles, the content lead has no screen that answers how much of the library is gated, which role gates the most content or which posts shipped during the last sprint without protection. Those are aggregate questions that the data answers but the per-post UI does not surface.

SleekView reads wp_posts joined to wp_postmeta on the Private Content / Restricted Content meta keys. Every gated post appears as one row with restriction type, allowed roles, enforcement mode and last update inline. Sortable on any column, filterable in combinations the meta box never surfaces, and inline-editable so the editorial team can correct a missed gate across the cohort in one pass.

Private Content / Restricted Content does the per-post gating job cleanly: editors set the rule, 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 confirm "the subscriber role still gates most premium content" or "this quarter's content drop shipped gated" with a manual audit.

The data is in wp_posts and wp_postmeta, well indexed. SleekView joins it and surfaces every gated post as one row in one workspace. 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.