SleekView for Restrict Content Pro: members & payments as tables
Restrict Content Pro stores members, payments, and subscription levels in dedicated custom tables. SleekView reads them so you can run member triage, payment audits, and renewal queues — all in one screen.
♾️ Lifetime License available
RCP members and payments together
Restrict Content Pro keeps its data in custom tables: rcp_memberships holds member-membership records with status, recurring flag, level ID, and renewal date, rcp_payments stores every transaction with status, amount, and gateway info, and rcp_subscription_levels defines the levels themselves. Discount codes live in rcp_discount_codes with usage tracked separately. Each table is keyed for direct SQL access, which means SleekView can read them without going through PHP wrappers.
RCP's default admin splits Members, Payments, and Subscription Levels into separate screens. The same operational questions that recur across membership plugins recur here: which members have failed payments, which are on recurring subscriptions versus one-time, what's the lifetime spend per member, who's at risk of churn. Reaching those answers requires the Reports tab or custom queries — not a row-level workspace.
SleekView reads rcp_memberships, rcp_payments, and rcp_subscription_levels directly and joins them on customer_id for member-centric views. The dunning queue becomes a saved filter on rcp_payments, lifetime spend becomes an aggregate sort, and the recurring-versus-one-time cohort becomes a column.
Workflow
RCP tables joined for member triage
Map the RCP tables
rcp_memberships, rcp_payments, and rcp_subscription_levels. Each becomes its own view with the columns RCP already maintains, and customer_id is the join key.
Join on customer_id
Save the workflow views
Edit through the RCP API
Sample columns
A typical RCP members view
wp_rcp_memberships + wp_rcp_payments + wp_rcp_subscription_levels
| Member | Level | Status | Lifetime | Last payment | Renewal |
|---|---|---|---|---|---|
| alex@studio.co | Premium | Active | $288 | Apr 24 | May 24 |
| ria@design.io | Annual | Active | $120 | Mar 14 | Mar 14 |
| tom@hello.dev | Premium | Pending | $24 | — | Apr 28 |
| mia@brew.coop | Trial | Cancelled | $0 | — | — |
Comparison
Default RCP admin vs SleekView
Default RCP admin
- Members, payments, and levels split across separate admin screens
- Joining payment status with member level needs reports
- Bulk status updates aren't first-class
- Filtering by level + recurring status + date isn't built in
- Failed-payment dunning views need custom queries
SleekView
- Joined member + payment views
-
Lifetime-spend column from
rcp_payments - Inline-edit member status and level
- Filter failed payments for dunning
- Save views per role
Features
What SleekView gives you for Restrict Content Pro
Joined RCP tables
Combine rcp_memberships with rcp_payments for a single member-centric view with payment history, level name, and renewal date visible inline. One row per member, all the relevant fields.
Dunning workflows
Filter rcp_payments by failed or refunded status, with member email and level for fast resolution. Sort by amount or date to prioritise the highest-value accounts in the queue.
LTV and cohorts
Aggregate lifetime spend per member by summing rcp_payments.amount; filter by membership join date to see cohort retention curves directly in the table.
Audience
Who uses SleekView for RCP
Finance
Failed-payment queues and lifetime-value rankings in one workspace. Filter by date range for monthly close; export the dunning queue as CSV for outreach campaigns.
Membership admins
Active vs cancelled members with inline level changes. Bulk-update across cohorts when restructuring level pricing or running comp programs.
Support
Per-member payment history at a glance during chat. Last payment, lifetime spend, and current membership status all on one row for full context.
The bigger picture
Why RCP stores need cross-table workspaces
Restrict Content Pro is built for membership sites that want clean separation between content access and billing — which is exactly why the data ends up split across tables that the default admin treats independently. The trouble is that membership operations don't separate cleanly. Every dunning workflow needs payments and memberships read together.
Every churn analysis needs recurring status from one table and renewal date from another. Every per-level revenue audit needs payments filtered by the level join. The Reports tab covers the aggregate views, but the row-level question — which specific members do I need to email today — still requires cross-screen navigation or SQL.
SleekView's joined view collapses that into one workspace. A finance lead can scan the failed-payments queue with member email and level visible, a support agent can pull up a single member's full payment history during chat, and a growth manager can rank members by lifetime spend and filter by recurring status to size up the autopay cohort. The data was always there in RCP's well-designed tables; SleekView just makes it visible together.
Questions
Common questions about SleekView for Restrict Content Pro
Yes. Discount codes from rcp_discount_codes are exposed as a separate view, with their usage joinable to payments via the discount-code metadata stored on each payment row. Build a discount-code performance view ranked by total uses and revenue impact.
Yes. Recurring status is a column on rcp_memberships and a first-class filter. Build a saved view of recurring members with upcoming renewals to see the autopay cohort, and a separate one-time-payment cohort for renewal-outreach campaigns.
Yes when SleekView uses RCP's API for status changes — registered hooks for renewal emails, gateway syncs, and access-control updates fire as expected. Direct DB edits skip hooks by design, which is the right choice for bulk migrations but the wrong one when emails should send.
Add-ons that store data in additional custom tables can be exposed as separate views; column-level support depends on whether the add-on uses standard SQL columns or serialised data. Most well-built RCP add-ons follow the core convention and work out of the box.
Yes. Save views and gate them by capability so finance sees the payment-amount columns, support sees the member-contact columns, and admin sees everything. The same underlying tables; different column projections per role.
Yes. Each subsite has its own RCP tables (or the network-wide tables if RCP is configured network-wide), and SleekView reads the current subsite's data only by default. Network-wide views can be configured explicitly when the membership data spans subsites.
Yes. Sort by expiration_date on rcp_memberships and filter to a future window — say, expiring in the next 14 days. Combine with recurring status filtered to off to find the non-recurring members who need a renewal email before they lapse.
Gateway IDs and transaction references live on rcp_payments as standard columns and surface as filterable values in SleekView. Build a per-gateway view to compare payment volume, failure rates, or refund counts across Stripe, PayPal, and any other gateways your store accepts.
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