User Role Membership leans on WordPress core: roles in wp_options, user-role assignments in wp_usermeta, and content restrictions stored in wp_postmeta. The plugin orchestrates them as a membership system without adding a parallel members table. Subscribers exist as standard WordPress users with one or more roles attached.

That makes the schema clean and the default reporting thin. The Users screen lists every account with a role column. The plugin's own settings configure which roles act as paying tiers and which content they unlock. Neither screen tells the operator how the role population is shaped this month, which paid role is growing or how much protected content each role tier actually accesses.

SleekView reads wp_users joined to wp_usermeta for role assignments and to wp_postmeta for the role-restriction rules. Every user appears with role, registration date, accessible-post count and last activity inline. Sortable on any column, filterable in combinations the Users screen does not surface together, and inline-editable so role changes route through wp_update_user and the standard WordPress hooks.

User Role Membership keeps the system honest by reusing WordPress roles for access, which is the right architectural call and the reason the default reporting is thin. The Users screen counts accounts but not paid-tier population, the plugin settings define which role unlocks what but do not surface the relationship per user, and the operator ends up running the weekly review off a spreadsheet exported from the Users page. SleekView joins wp_users, wp_usermeta and the role-restriction postmeta into one workspace.

The paid-tier KPI sits next to the role population view, the per-role accessible-post column confirms each tier unlocks what marketing promised, and the signup trend filters scope the cohort to the window under review. Same WordPress role primitives the plugin already uses, organised as the cockpit they deserve.