SleekView for Paid Memberships Pro Add-ons: bundled add-on data as tables
PMPro's add-ons store approvals, sponsored relationships, multi-membership assignments, and registration-helper data in their own tables and meta keys. SleekView reads them all and joins to wp_pmpro_memberships_users for a single member view.
♾️ Lifetime License available
Add-on data joined to the PMPro core roster
The Paid Memberships Pro add-on library extends the core plugin with focused features: Approvals adds an approval queue, Sponsored Members links sub-accounts to a sponsor, Multiple Memberships per User lets a single user hold concurrent levels, Register Helper introduces custom registration fields, and the various reports add-ons emit cached aggregates. Each add-on writes to either its own table or wp_usermeta with add-on-prefixed keys.
The default admin shows each add-on as its own screen or tab. The approval queue is its own screen. Sponsored relationships have their own column on the members view but not their own cohort view. Multiple memberships per user are visible per-user but not as a roster. Cross-add-on questions (show me approved members on more than one level with completed sponsor relationships) need either custom SQL or piecemeal exports.
SleekView reads each add-on table or meta key as a standard data source and joins them to wp_pmpro_memberships_users on user_id. The approval queue becomes a filter, the sponsored-relationships graph becomes a joined column, and Register Helper fields become first-class columns alongside the core PMPro data.
Workflow
PMPro core joined to its add-on data
Map the add-on tables and meta
wp_usermeta keys. Each becomes a navigable data source.
Join on user_id and level_id
user_id.
Save the workflow views
Edit through the add-on APIs
Sample columns
A typical PMPro add-on members view
wp_pmpro_memberships_users + add-on tables + wp_usermeta (add-on keys)
| Member | Level | Approval | Sponsor | Levels held | Status |
|---|---|---|---|---|---|
| alex@studio.co | Pro | Approved | studio HQ | 2 | Active |
| ria@design.io | Annual | Approved | . | 1 | Active |
| tom@hello.dev | Pro | Pending | hello.dev | 1 | Past due |
| mia@brew.coop | Free | Rejected | . | 0 | Cancelled |
Comparison
Default PMPro add-ons admin vs SleekView
Default PMPro add-ons admin
- Each add-on has its own screen, no cross-add-on cohort view
- Approval queue cannot be filtered alongside payment status
- Sponsored relationships are not a first-class cohort column
- Multiple memberships per user are visible per-user, not as a roster
- Register Helper fields are not surfaced in the members table
SleekView
- All add-on tables joined to the PMPro core roster
- Approval state, sponsor, and multi-level columns inline
- Register Helper fields as sortable, filterable columns
- Cohort views across approval, payment, and level
- Inline approvals and bulk approve through the add-on API
Features
What SleekView gives you for Paid Memberships Pro Add-ons
Approvals as a filter
Surface the Approvals add-on's approval state as a column on the main member roster. Filter to pending applications and approve inline, or run a bulk approve through the add-on's API.
Sponsored relationships
Join the Sponsored Members add-on data so each sub-account shows its sponsor on one row. Group by sponsor to audit corporate roll-ups; filter by sponsor for per-account ops.
Multi-membership roster
Members holding more than one PMPro level via the Multiple Memberships per User add-on render with each level inline. Sort by levels-held count to spot power users and trial overlaps.
Audience
Who uses SleekView for Paid Memberships Pro Add-ons
Membership admins
Approval queue and sponsor relationships in one view. Filter pending approvals by registration date; bulk-approve a cohort once vetting completes.
Finance ops
Sponsored corporate accounts rolled up by sponsor for invoicing audit. Multi-level members for revenue attribution across overlapping cohorts.
Support
Per-member approval state, sponsor, and Register Helper field values visible during chat. Inline approval flips for cases that need quick action.
The bigger picture
Why the add-on stack needs joined tables
PMPro stays lean by keeping its core small and offloading features to add-ons. That is the right architectural choice, but it means operational data ends up spread across the core members and orders tables plus each enabled add-on's tables or wp_usermeta keys. The default admin reflects that split: Approvals, Sponsored Members, Multiple Memberships, and Register Helper each have their own screen or column, but no single screen consolidates them.
A real ops question (approved members on the Pro level with completed sponsor relationships and recent failed payments) needs cross-add-on data. SleekView reads each add-on as a standard data source and joins them to the core roster on user_id. The approval queue becomes a filter, the sponsor roll-up becomes a saved view, and Register Helper fields become first-class columns.
Admins, finance, and support each get the slice they actually need.
Questions
Common questions about SleekView for Paid Memberships Pro Add-ons
Yes. The add-on stores approval state on a per-user level basis. SleekView surfaces it as a column on the members roster, and inline approval flips route through the add-on's API so notification hooks fire.
 
The Sponsored Members add-on stores sponsor relationships in wp_usermeta with add-on-prefixed keys. SleekView joins them so each sub-account shows its sponsor inline and sponsor-level rollups become saved views.
Yes. With the Multiple Memberships per User add-on enabled, members holding more than one level render as one row per active level with the user_id grouping intact. Group by user_id to collapse, or treat each level as its own row.
 
Yes. Register Helper stores custom registration fields in wp_usermeta with field-specific meta keys. SleekView surfaces each as a sortable, filterable column on the members view.
PMPro's reports add-ons emit cached aggregates into their own tables. SleekView reads them as additional data sources so report data can be filtered, joined to members, or exported.
 Yes when SleekView routes status, approval, and level writes through the PMPro and add-on APIs. Registered hooks (notifications, capability sync) fire as expected. Direct DB writes remain available for bulk operations.
 Yes. Save column sets per WordPress capability so finance sees amounts, support sees approval state and contact, admins see everything. Each role loads only the data it needs.
 Yes. Queries are paginated and use the indexed user_id columns PMPro and its add-ons maintain on their tables and meta. Sites with hundreds of thousands of members run smoothly because joins use existing indexes.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Funnelkit Stripe Gateway
- Woocommerce Side Cart
- Woocommerce Affiliatewp Integration
- Givewp
- Woocommerce Mirakl
- Woocommerce Hermes Shipping
- Woocommerce Snapchat Pixel
- Woocommerce Shipping Canada Post
- Yith Subscriptions
- Paykickstart Bridge
- Surecart Cart
- Woocommerce Currency Converter
- Woocommerce Tax Jar
- Woocommerce Sezzle
- Woocommerce Quick View