WishList Member writes each member's level assignment into wp_usermeta under the wlm_levels key plus per-level state keys. State values include Active, Cancelled, Expired, Incomplete, and pay-per-post positions. The plugin also stores last-payment status and the next billing event per level via gateway metadata that lands on the user profile. The default Manage Members screen lists members across all levels and filters by one state at a time.

SleekView Kanban reads wp_usermeta for the wlm keys and joins to wp_users. It groups members by the level state for a chosen membership level and shows one card per member. Card titles use display_name, meta lines show the level name, the recurring price configured on that level, the next billing date pulled from gateway meta, and the last payment status. Filter the board by level, by gateway, by signup date, or by any custom wlm meta key like sequence position.

Drag a card from Active into Cancelled and SleekView calls the WLM cancellation action so gateway subscriptions stay in sync and content protection rules recompute. Drag a card from Incomplete into Active to manually unlock a member after a successful manual charge. Failed writes leave the card in its column and surface the gateway error on the card front so the operator can fix the underlying issue.

WishList Member stores rich state per member, per level, but it surfaces that state through a per-member edit screen and a paginated members table. For sites running several levels at once, that UI hides the questions an operator actually needs answered. How many Inner Circle members are stuck in Incomplete after signup.

How many trial members will auto-convert tomorrow and who needs a personal note first. How many members expired this week with a recoverable card error. A kanban board groups members by level state and shows those questions next to each other on one screen, with one card per member.

Because the board reads wlm usermeta live and writes back through the documented WLM actions, it is not a parallel system. It is the same state the rest of the site checks for content protection, simply rendered as columns. The result is that operators can act on the recurring-revenue questions without ever opening a member edit screen until they actually need to.