Restrict Content (the free version, by Pippin Williamson, now StellarWP) is intentionally lightweight. Membership status sits in usermeta under keys like rcp_status, rcp_subscription_level, rcp_expiration, and rcp_joined_date. Per-post access rules live in postmeta on each restricted post. The default admin shows a basic users-with-membership list; everything beyond that requires opening individual profiles.

SleekView reads the meta directly and gives admins flat, sortable, inline-editable views across both surfaces. The members view joins wp_users with the rcp_* usermeta keys so primary role, level, status, and expiration all become real columns. The restricted-content view reads postmeta to surface every post with its required level — the audit view content managers actually need.

Renewal outreach lives or dies on the "expiring next 14 days" filter, and that filter requires expiration as a sortable column. SleekView builds it from existing data. Inline edits write through standard WordPress meta APIs, so any plugin or custom code listening for rcp_status changes fires the same way it would through the dashboard.

Restrict Content's design choice — store everything in WordPress's native usermeta and postmeta — is correct for the plugin's positioning, which is to be the simple, lightweight alternative to heavier membership plugins. The trade-off is that the admin surface inherits WordPress's limitations: usermeta isn't queryable as columns in the default users screen, postmeta isn't visible in the posts list, and cross-cutting questions like "every restricted post requiring Premium" or "every member whose Pro membership expires within two weeks" require either custom code or a third-party reporting plugin. Membership ops lives on these queries.

Renewal outreach is timing-sensitive and segment-specific; content audits matter because mis-restricted content (free content accidentally locked, or premium content accidentally public) silently degrades the membership offer. A flat, filterable view across both surfaces — members and restricted posts — gives the team the operational visibility the plugin's lean storage choice deliberately doesn't include in its own admin.