Indeed Ultimate Membership (commonly called IHC) stores its operational data in dedicated tables: wp_ihc_user_levels holds per-user level assignments with status (active, pending, expired), wp_ihc_transactions records every charge, refund, and gateway response, and wp_ihc_subscriptions tracks recurring subscription state. Membership levels themselves are defined in plugin options, and content-restriction rules live in wp_postmeta on protected posts under IHC-prefixed keys.

The default IHC admin gives separate screens for Members, Transactions, Subscriptions, and Settings. Joining a user's current level state to their transaction history means navigating between two screens or using the Reports tab. Recurring-subscription health (which subscriptions failed renewal in the last week) doesn't surface as a top-level view; it requires filtering the transactions tab manually.

SleekView reads the three IHC tables directly, joins wp_ihc_user_levels to wp_ihc_transactions on user ID, and exposes per-user level state with lifetime spend and last-transaction outcome as proper columns. The failed-renewal cohort becomes a saved filter; bulk level corrections happen through the IHC API for hook-safe writes.

IHC Membership stores its operational data in proper custom tables, which is exactly the right architectural choice for a plugin handling thousands of recurring transactions per month. The data model supports any cross-table question: who's active per level, whose last transaction failed, which levels have the highest lifetime spend, which subscriptions stopped renewing. What the default admin lacks is the operational workspace that exposes those questions as row-level views.

Every cross-table query becomes the Reports tab or custom SQL. SleekView turns the IHC schema into a workspace: user levels joined to transactions and subscriptions, with status and lifetime spend as sortable columns and the failed-renewal cohort as a saved filter. Finance teams reconcile monthly close in one view; membership admins triage level state at the table level; support staff see full member context on every ticket.

The data was always there. SleekView just makes it look like the operational tool an active membership business actually needs.