The Paid Membership add-on for LearnPress gates course access through subscription plans recorded as wp_posts (post_type=lp_order) with status meta tracked in wp_postmeta, while per-user course state lives in wp_learnpress_user_items. The default LearnPress orders screen shows individual transactions; the add-on layers plan access on top, but there's no built-in screen that combines plan tier with current course progress for a given subscriber.

SleekView reads the order posts and the learnpress_user_items rows directly. A subscriber roster joins both tables so each member row shows current plan, plan expiry date, the courses unlocked under that plan, and progress percentages per course. An expiring-plan queue filters _lp_membership_end_date for the next 14 days. A plan-versus-progress view answers a question the default admin can't: who paid for the higher tier but never started the bonus courses, who's burning through their plan content and is a candidate for an upsell.

Inline edits to order status route through LearnPress's order API where supported so plan-renewal hooks fire and email notifications send. Direct table edits skip hooks for back-fill operations like correcting historical plan-end dates. Multisite networks scope views per subsite, and capability gating ensures finance sees billing detail while instructors see only progress data.

Paid-membership LMS sites carry two operational realities that the default admin treats as separate problems. There's the billing reality (who paid, when does it lapse, who's overdue), and there's the learning reality (who's using what, who's stalled, who's about to finish). Both live in the database, but the default LearnPress admin keeps them on different screens, and the Paid Membership add-on layers plan-tier logic without reshaping how the data is browsed.

Finance needs the renewal queue with progress context so outreach copy lands right. Support needs a single-row member summary so chat tickets close quickly. Instructors want plan-scoped cohorts so they know who's still entitled to their content.

Marketing wants upsell cohorts (used a lot on a small plan, paid for a big plan and barely showed up) that the default admin can't compose. SleekView's job is to expose lp_order and learnpress_user_items as a shared workspace so each team builds the view their job actually requires, with hooks fired or skipped per view, and capability gating that keeps the right data visible to the right people.