✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Paid Memberships Pro

Paid Memberships Pro writes every member to pmpro_memberships_users with a status of active, inactive, cancelled, expired, or admin_cancelled, and every payment to pmpro_membership_orders. SleekView Kanban reads those rows and turns status into draggable columns, one card per member.

♾️ Lifetime License available

SleekView Kanban board for Paid Memberships Pro

Read PMPro members as a pipeline, not a paginated members list

Paid Memberships Pro stores every membership row in pmpro_memberships_users with status values of active, inactive, cancelled, expired, admin_cancelled, and admin_changed. Recurring payments and one-off charges sit in pmpro_membership_orders with their own status of success, pending, error, refunded, and review. The default Members admin page is a list with a status dropdown, so you only ever look at one status at a time.

SleekView Kanban reads pmpro_memberships_users joined to users and pmpro_membership_levels and groups rows by status. Each row becomes a card showing the member name, the level name, the initial payment or billing amount from the level, and the most recent order status pulled from pmpro_membership_orders. Filter by level, by billing cycle, by signup date, by gateway, or by any user meta key.

Drag a card from Active into Cancelled and SleekView calls pmpro_changeMembershipLevel with the cancellation reason, which fires the official cancellation hooks, cancels the gateway subscription, and writes the row to pmpro_memberships_users with status cancelled. Drag a card into Expired manually for cases where the gateway already lapsed but PMPro has not run the daily cron yet. Failed writes leave the card in its column and surface the gateway error on the card front.

Workflow

From pmpro_memberships_users to a kanban in four steps

1

Point SleekView at PMPro

Add a SleekView data source for pmpro_memberships_users joined to users on user_id and pmpro_membership_levels on membership_id. SleekView exposes status, level name, initial payment, billing amount, and any user meta you store.
2

Pick status as the column key

Switch the view type to Kanban and pick status as the grouping. Active, inactive, cancelled, expired, and admin_cancelled become columns. Hide any you do not use, reorder so your review priority sits on the left edge of the board.
3

Choose what shows on each card

Set the card title to display_name from users, add meta lines for membership level, billing amount, and last order status. Add a badge for gateway so Stripe, PayPal, and Authorize.Net members render with their own colour on the board.
4

Enable drag-and-drop writes

Turn on write-back so dragging into Cancelled fires pmpro_changeMembershipLevel with the cancellation reason. Restrict the action to the pmpro_membership_manager capability so only billing roles can move cards between member states.

Sample board

Sample PMPro members board

Four columns reading from pmpro_memberships_users, grouped by status, with member, level, and billing amount visible on each card.
Pending
17
Noah Bennett, Annual
$120/yr, Stripe checkout started
Yara Haddad, Monthly
$15/mo, PayPal review hold
Marcus Lin, Lifetime
$399 one-off, wire transfer queued
Active
942
Elena Vargas, Annual
$120/yr, renews 2026-11-04
Caleb Andersson, Monthly
$15/mo, renews 2026-06-21
Ines Romero, Lifetime
Paid 2024-07-12, no renewal
Cancelled
208
Patrick Fowler, Monthly
Cancelled 2026-05-22, access ends 2026-06-22
Asha Kothari, Annual
Cancelled at period end, exp 2026-08-04
Greg Mahon, Monthly
Cancelled by gateway, dispute lost
Expired
634
Sofia Ricci, Annual
Expired 2026-05-30, last charge failed
Otis Gallagher, Monthly
Expired 2026-05-12, card lapsed
Joon Park, Annual
Expired 2026-04-18, no renewal attempt

Comparison

Default PMPro members screen vs SleekView Kanban

Default PMPro members list

  • Members screen filters to one status at a time, so cancelled and expired are never side by side
  • Cancelling needs an edit-member round trip per row, no drag of a batch of dunning members at once
  • No card layout, so member name, level, billing amount, and last order status never sit on one tile
  • Expired members blend into the same paginated list as healthy active subscribers
  • Admin cancellations and member cancellations look identical until you open each member edit screen

SleekView Kanban

  • Reads pmpro_memberships_users and pmpro_membership_orders live, no nightly sync
  • Drag-and-drop writes call pmpro_changeMembershipLevel so gateways stay in sync
  • Filter by membership level, gateway, signup date, or any wp_usermeta key
  • Card meta supports computed values, e.g. lifetime spend summed from pmpro_membership_orders
  • Per-role visibility, so only roles with pmpro_membership_manager can move cards between statuses

Features

What SleekView Kanban gives you for Paid Memberships Pro

Status writes back to PMPro

Dragging into Cancelled calls the documented pmpro_changeMembershipLevel hook with the cancellation reason. Gateway subscriptions cancel, access rules recompute, and the row in pmpro_memberships_users gets the right status. Failed writes leave the card in its original column with the error visible on the front.

Stack filters per board

Filter by membership level, by gateway, by billing amount, by country, by any wp_usermeta key. Save filter sets per board so the dunning board, the new-signup board, and the cancellation review board each open scoped to the right slice of members.

Member context on every card

Card titles show display_name, meta lines show level, billing amount, next renewal date, and last order status. Click a card to jump straight to the PMPro edit-member screen for the full record without losing the board state.

Audience

Where PMPro sites put the Kanban board

Dunning and recovery review

An Expired column scoped to the last 30 days lists every member whose last order failed. Billing reads the gateway error on each card and drags recoverable members back to Active after a manual charge succeeds.

Onboarding queue

Pending and just-Active columns show signups from the last 14 days. The membership lead works the queue card by card, sending a personal welcome and tagging accounts for the welcome email automation.

Cancellation save desk

A board filtered to Cancelled within the last 7 days groups members by cancellation reason captured at cancel time, so save outreach focuses on reasons the team can actually act on.

The bigger picture

Why the kanban view matters for Paid Memberships Pro

PMPro is a fully featured membership stack that exposes every billing event as a clear row in pmpro_memberships_users and pmpro_membership_orders. The trouble is that the default admin treats those rows as a paginated list and asks you to filter to one status at a time. Operationally the questions that move revenue are status questions.

How many members are pending the first charge today. How many are expired this week and could be reached before they churn for good. How many were admin_cancelled by a billing rule that should never have fired.

A list view buries those answers behind dropdowns. The kanban view shows them next to each other so the operator can act without context switching. Because SleekView reads pmpro_memberships_users live and writes back through pmpro_changeMembershipLevel, the board does not become a second system to keep in sync.

It is the same data, the same gateway state, the same membership level changes, simply rendered as a board with cards. The win is not the drag-and-drop itself, it is starting the day already looking at the work that pays the bills.

Questions

Common questions about SleekView Kanban for Paid Memberships Pro

Yes. Cancellation writes go through pmpro_changeMembershipLevel, the same function called by the PMPro admin Cancel button. The gateway cancel API fires for Stripe, PayPal, Authorize.Net, or any add-on gateway, the row in pmpro_memberships_users updates, and access rules recompute. Failed gateway calls leave the card in its original column and show the error on the card.

 

By default the PMPro statuses become columns: active, inactive, cancelled, expired, admin_cancelled, and admin_changed. Hide ones you do not use, reorder them, and add a synthetic Failed column built from pmpro_membership_orders where status is error or review in the last 30 days for a dunning-focused board.

 

Yes. Point the data source at pmpro_membership_orders and the order statuses become the columns: success, pending, error, refunded, and review. This is the right setup for sites that want a refund-review board or a payment retry queue rather than a member lifecycle board.

 

Yes. The Approval add-on stores its state in usermeta on each member. SleekView reads usermeta as a derived column, so an Approval kanban with columns pending, approved, denied works alongside the standard status board without any code changes.

 

Yes. Card meta supports joins and aggregates. Common computed fields are lifetime spend summed from pmpro_membership_orders, days since last successful charge, and total renewals. These compute server side and cache per filter set so the board stays responsive.

 

SleekView paginates per column with a configurable card limit, reads pmpro_memberships_users on the indexed status column, and caches column counts per filter set. Boards stay responsive on six-figure member counts because no single column tries to render more than its current page of cards at a time.

 

Yes. Drag-and-drop writes are gated behind any WordPress capability you choose. Common setups give pmpro_membership_manager full write access, while a support role sees the same board read-only. Card click-through to the member edit screen also respects PMPro capability checks.

 

No. The PMPro admin stays the source of truth for membership levels, billing rules, and add-on settings. SleekView Kanban is a reading and quick-action layer on top of pmpro_memberships_users. Every card links to the underlying PMPro edit-member screen for the cases where you need the full record.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView