Groups Paid Membership sits on top of the Groups plugin, which stores group definitions in wp_groups_group and user-to-group assignments in wp_groups_user_group. Capabilities granted by group membership land in wp_groups_capability and wp_groups_group_capability. The paid layer adds subscription orders, typically backed by WooCommerce subscriptions or custom subscription posts depending on the configured gateway, and writes group-assignment expiry to wp_groups_user_group meta.

The default Groups admin shows groups in one list and users in another. To answer "which paying members lost their group assignment because their subscription expired," the default UI requires cross-checking the Groups user list against the WooCommerce subscriptions list manually. Capability inheritance (which groups grant which capabilities to which users) needs three separate screens to trace.

SleekView reads wp_groups_user_group joined to wp_users and to the subscription source (WooCommerce or custom), and exposes the group plus subscription state as one row per member. Capability inheritance becomes a navigable column. Expiry mismatches (subscription cancelled but group still assigned) become a saved filter.

The Groups plugin pairs naturally with paid subscriptions: a group represents a paid tier, and the subscription represents the payment that keeps the user in the group. The pairing only works if the two stay in sync. In practice, webhook failures, manual interventions, and race conditions create drift: subscriptions get cancelled without removing the group, or groups get removed while the subscription keeps renewing.

Both modes silently break the product. Groups Paid Membership stores everything needed to detect drift, but the default admin keeps groups and subscriptions on separate screens, so the audit becomes a manual cross-check. SleekView turns the cross-check into a single workspace: groups joined to subscriptions on user ID, capability inheritance surfaced inline, drift filtered as a saved view.

Membership admins fix orphaned assignments before they become refund requests; finance teams reconcile paying-vs-entitled members each month; compliance teams document capability inheritance for external audits. The plugin architecture was always sound. What it needed was the row-level workspace to actually run the operational checks.