Paid Member Subscriptions, the Cozmoslabs plugin, stores every member subscription as a row in pms_member_subscriptions with status, subscription_plan_id, user_id, billing_amount, billing_next_payment, and a record of the payment gateway. The official screen shows these as a paginated list with a status filter on top, which is fine for one member but heavy when a member success team needs the whole base on one screen.

SleekView reads pms_member_subscriptions directly and joins to wp_users for the member name and pms_subscription_plans for the plan title. The status column is the natural one to group by, so the board shows one column per real status the table contains. Active, Pending, Expired, Cancelled, and Abandoned populate with their actual counts, and member name, plan title, billing amount, and next payment date ride on the card front.

Drag a Pending card to Active when payment lands and SleekView writes the new status back through the standard PMS update flow, so the same role assignments and renewal emails fire as on the official screen. Expired and Cancelled columns sit on the right, filters scope the board to one plan when the catalogue is large, and saved views give success, finance, and retention their own scoped reading of the same table.

Paid Member Subscriptions is built around the idea that a member subscription is a stateful object. Active grants access, Pending awaits payment, Expired drops access until renewal, Cancelled has explicitly ended. Every product decision in PMS reflects that.

The default screen, though, is a paginated list with a status filter on top, which makes it easy to look at one status at a time and hard to see the whole base together. SleekView Kanban reads the same pms_member_subscriptions table and groups by the status column directly, so Pending, Active, Expired, and Cancelled appear side by side with their counts. Success saves a board for Pending and Expired across every plan, plan owners save boards scoped to one plan, finance saves a board for renewals due this week.

Dragging a card runs through the PMS subscription update so role assignments and emails fire exactly the same way, only the way the team reads the base changes.