SleekView Kanban for Restrict Content Pro
Restrict Content Pro writes every membership to rcp_memberships with a status of active, pending, cancelled, or expired, and every payment to rcp_payments. SleekView Kanban reads those rows and turns the status column into draggable columns, one card per member.
♾️ Lifetime License available
Read RCP memberships as a pipeline, not a paginated table
Restrict Content Pro keeps a clean schema. Every membership row sits in rcp_memberships with status values of active, pending, cancelled, and expired, plus customer_id, object_id for the level, initial_amount, recurring_amount, and expiration_date. Payments live in rcp_payments with their own status of complete, pending, failed, refunded, and abandoned. The default Memberships admin page is a sortable table that filters one status at a time.
SleekView Kanban reads rcp_memberships joined to rcp_customers, rcp_membership_levels, and users. It groups rows by status and renders each row as a card with the customer name, the level name, the recurring amount, and the expiration date. Filter by level, by gateway, by signup date, by country pulled from usermeta, or by any field stored on the customer row.
Drag a card from Active into Cancelled and SleekView calls RCP_Membership::cancel, which is the same method the RCP admin Cancel button calls. The gateway cancel API fires for Stripe, PayPal, Authorize.Net, and Braintree, the membership status flips, and any restricted content rules recompute. Drag a card from Pending into Active to manually approve a membership held for review. Failed writes leave the card in place and show the gateway error on the card front.
Workflow
From rcp_memberships to a kanban in four steps
Point SleekView at RCP
Pick status as the column key
Choose what shows on each card
Enable drag-and-drop writes
Sample board
Sample RCP memberships board
Comparison
Default RCP memberships table vs SleekView Kanban
Default RCP memberships
- Memberships screen filters to one status at a time, so dunning and active are never side by side
- Cancelling requires opening each membership in turn, no batch drag of expired members
- Card layout missing, so customer, level, recurring amount, and expiration never sit on one tile
- Trialing memberships look identical to paid actives until you open each one
- Pending signups are buried behind a filter rather than visible at the start of the daily queue
SleekView Kanban
-
Reads
rcp_membershipsandrcp_paymentslive, no extract or scheduled sync -
Drag-and-drop writes call
RCP_Membership::cancelso gateway state stays correct - Filter by membership level, gateway, expiration window, or any rcp_customer field
- Card meta supports computed columns, e.g. lifetime spend summed from rcp_payments
- Per-role visibility, so only roles with rcp_view_members can move cards between states
Features
What SleekView Kanban gives you for Restrict Content Pro
Status writes back to RCP
Dragging into Cancelled fires the official RCP_Membership::cancel method so Stripe, PayPal, Authorize.Net, or Braintree gateways stay in sync. Restricted content rules recompute automatically. Failed writes leave the card in place and surface the gateway error directly on the card front.
Filter by anything on the customer
Stack filters for membership level, gateway, country, signup date, or any custom field on rcp_customers. Save filter sets per board so a recovery board, a new-signup board, and a renewal-window board each open scoped to the right slice.
Customer context on each card
Cards show customer name, level, recurring amount, expiration date, and gateway badge. Click a card to open the underlying rcp_membership in the RCP admin edit screen without losing the board state.
Audience
Where RCP teams put the Kanban board
Dunning review
An Expired column scoped to the last 30 days lists every membership whose last payment failed. Billing taps each card to read the gateway error and drags recovered ones back to Active after a manual charge.
Approval queue
Sites that hold new signups for manual review keep a Pending column on the board. The admin reads each new card, verifies the signup, and drags into Active to approve.
Renewal outreach
Filter the Active column to expiration_date within the next 14 days. The customer success team works the cards card by card, sending renewal nudges with the right level and amount in the email.
The bigger picture
Why the kanban view matters for Restrict Content Pro
RCP is one of the cleanest membership plugins on the market because every billing event maps to a clear row in rcp_memberships or rcp_payments. That makes the data trivial to query, but the default UI still treats each row as a line in a paginated table. The operational questions that drive membership revenue are status questions.
How many memberships are pending the first charge. How many are expired this week and worth a recovery attempt. How many active memberships expire inside the next two weeks and need a renewal nudge.
A list view answers one of those at a time. A kanban view answers all of them on one screen. Because SleekView reads rcp_memberships live and writes back through RCP_Membership::cancel, the board is not a parallel system.
It is the same data, the same gateway state, the same restricted content rules, simply rendered as columns with cards. The operational saving is not the drag itself, it is starting the day already looking at the work that grows or saves recurring revenue.
Questions
Common questions about SleekView Kanban for Restrict Content Pro
Yes. Cancellation writes call RCP_Membership::cancel, the same method the RCP admin Cancel button calls. The gateway cancel API fires for Stripe, PayPal, Authorize.Net, or Braintree. The row in rcp_memberships updates to status cancelled and any restricted content rules recompute. Failed gateway calls leave the card in its original column with the error on the front.
By default the four RCP statuses become columns: pending, active, cancelled, and expired. You can hide ones you do not use, reorder them, and add a synthetic Failed column built from rcp_payments where status is failed or abandoned in the last 30 days for a dunning-focused board.
Yes. Point the data source at rcp_payments and the payment statuses become the columns: complete, pending, failed, refunded, and abandoned. This setup is useful for refund review queues or for a board focused on retrying failed charges.
Yes. Trialing memberships sit under Active in rcp_memberships, but you can add a derived column that flags trialing rows and render them with a different badge or a dedicated Trialing column on the board. The board respects trial-end dates so renewal forecasts include trial conversions.
Yes. Card meta supports aggregates, so lifetime spend summed from rcp_payments, count of renewals, and days since last successful payment all render directly on the card. These compute server side and cache per filter set.
SleekView paginates each column with a configurable card limit, queries rcp_memberships on the indexed status column, and caches column counts per filter set. Even on six-figure customer counts the board renders fast because no single column tries to load more than its current page of cards.
Yes. Drag-and-drop writes are gated behind any WordPress capability you select. The default uses rcp_view_members, but you can map a custom role so support agents see the same board with cards locked, while only billing managers can move members between statuses.
No. The RCP admin stays the source of truth for membership levels, payment gateways, restriction rules, and discount codes. SleekView Kanban is a reading and quick-action layer on top of rcp_memberships. Every card links to the underlying RCP edit-membership screen for the cases that need the full editor.
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 checkout