✨ 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 for Restrict User Access Pro: access levels and user assignments as tables

Restrict User Access Pro stores access levels as the restrict post type and tracks per-user assignments via wp_usermeta keys. SleekView reads both so admins can audit who has which level, when it expires, and which conditions apply.

♾️ Lifetime License available

SleekView table view for Restrict User Access Pro

Access levels and user assignments in one workspace

Restrict User Access Pro (RUA Pro) models access control around access levels: each level is a restrict custom post type entry with one or more condition groups in postmeta describing what content the level protects and how. Per-user level assignments are stored in wp_usermeta under keys like _ru_member_level and _ru_member_level_expiry, with optional expiry timestamps per assignment. The plugin also handles role-based access by joining its own access levels to WordPress roles.

The default RUA admin gives each access level its own edit screen with conditions and synchronised roles. Per-user assignments are visible on the user-profile edit screen one user at a time. Asking "every user with the Pro access level whose expiry is in the next 14 days" or "every level that protects a specific post type" needs the reports module if available, exports, or direct usermeta queries. There's no row-level workspace that joins access levels to their assigned users.

SleekView reads the restrict post type and the per-user assignment usermeta keys together. Levels appear as a sortable, filterable table with member count, condition summary, and synced role visible inline. User assignments appear as a parallel view with the level name, expiry, and last-update timestamp as proper columns. Inline edits to user-level assignments route through RUA's own functions so registered hooks fire.

Workflow

RUA levels and user assignments in one workspace

1

Map the RUA sources

Point SleekView at the restrict post type (for level definitions) and the _ru_member_level + _ru_member_level_expiry usermeta keys (for user assignments). Each becomes a navigable view.
2

Compose the audit columns

Build the assignment view joining usermeta to wp_users for email and to the restrict post type for the level name. Expiry, status, and last-update timestamp render as proper columns.
3

Save the audit views

Save views for the renewal cohort (expiring soon), the expired-but-still-assigned cleanup list, the condition audit by protected content category, and the synced-role mapping. Gate by role for renewal ops, compliance, support, and admin.
4

Edit through RUA

Assignment and expiry writes go through RUA's own functions so registered hooks fire. Direct DB writes stay available for bulk migrations or one-off cleanup.

Sample columns

A typical Restrict User Access Pro assignments view

Per-user access level assignments joined to wp_users and the restrict post type for the level name.
Source: wp_posts (post_type=restrict) + wp_postmeta + wp_usermeta (_ru_member_level keys)
User Email Access level Status Expiry Assigned
Alex Studio alex@studio.co Pro Active Jun 24 Apr 24
Ria Design ria@design.io Annual Active Mar 14 2027 Mar 14
Tom Hello tom@hello.dev Pro Expiring May 20 Apr 24
Mia Brew mia@brew.coop Trial Expired Apr 02 Mar 02

Comparison

Default Restrict User Access Pro admin vs SleekView

Default RUA admin

  • Per-user level assignments in wp_usermeta view one user at a time
  • No cohort view of users by access level + expiry window
  • Condition groups in wp_postmeta aren't first-class filters
  • Bulk assignment changes across many users go one row at a time
  • Synced-role audits need direct queries

SleekView

  • Joined level and user-assignment views in one workspace
  • Filter by access level plus expiry window plus status
  • Surface RUA condition groups as a filterable column
  • Inline edit user-level assignments through RUA's own functions
  • Save audit views per role for admin and compliance

Features

What SleekView gives you for Restrict User Access Pro

Access-level table

List every restrict post-type level with member count, condition summary, synced role, and last-edit timestamp as columns. Sort by member count to find the most-assigned levels; filter by condition for protected-content audits.

User-assignment audits

Parallel view of per-user assignments from wp_usermeta keys (_ru_member_level, _ru_member_level_expiry) joined to wp_users. Filter by access level plus expiry window for renewal cohorts.

Inline assignment changes through RUA

Change a user's access level or expiry inline and SleekView calls RUA's own functions so any registered hook (capability sync, integration webhook) fires on save. Bulk apply across a filtered cohort in one action.

Audience

Who uses SleekView for Restrict User Access Pro

Renewal ops

Expiry-window audit of every user whose access level expires in the next 14 days, joined to the level name. Filter by level for targeted renewal outreach; bulk-extend expiry inline for legitimate edge cases.

Compliance

Synced-role and condition audit table showing exactly which roles map to which levels and which content categories each level protects. Filter by condition for periodic compliance reviews.

Support

Per-user access context visible during chat: current level, expiry, recent assignment changes, and the synced role. Full context on every access question without leaving the table.

The bigger picture

Why access control needs row-level audits

Access control plugins protect content; audit tooling makes sure they keep protecting the right content for the right people. Restrict User Access Pro stores level definitions in the restrict post type and per-user assignments in usermeta, which is the right schema for fast resolution but the wrong shape for cohort audits in the default admin. Renewal ops needs to see every user expiring this fortnight, not click through a list one at a time.

Compliance needs to see which levels protect which content categories, not edit one level at a time. SleekView turns RUA's two stores into joined tables where those audit questions are single saved views. Renewal outreach runs in minutes; compliance reviews happen quarterly with confidence; support sees full per-user context during chat.

The underlying schema stays authoritative; the workspace just makes it legible at the cohort level the default admin doesn't surface.

Questions

Common questions about SleekView for Restrict User Access Pro

Yes. The Pro extension uses the same restrict post type and usermeta keys as the free plugin, with additional fields for expiry and condition complexity. SleekView reads the same schema in both editions.

 

Yes when SleekView uses RUA's own functions for assignment changes and expiry updates, so any registered hooks (capability sync, integration callbacks) fire on inline edits. Direct DB edits to usermeta skip hooks by design.

 

Yes. Condition groups in wp_postmeta reference the post types or specific content they protect. Filter the level view by condition value to see exactly which access levels gate which content categories, useful for periodic compliance reviews.

 

Yes. Filter _ru_member_level_expiry to a date range (e.g. the next 14 days) and combine with a level filter to see exactly which users on the Pro or Annual level are coming up for renewal.

 

Yes. SleekView queries are paginated and use the indexed columns RUA already maintains on usermeta. Sites with hundreds of thousands of users with assignments run smoothly because joins happen on indexed user_id columns.

 

Yes. Save views per WordPress capability so renewal ops sees the expiring cohort, compliance sees the condition audit, and support sees per-user context. Each role only loads the data it needs.

 

Yes. RUA Pro syncs access levels to WordPress roles. The level view surfaces the synced role as a filterable column so admins can audit role-to-level mappings without leaving the table, useful when WordPress roles are also driving capabilities outside RUA.

 

Yes. Any SleekView view exports to CSV or JSON, including joined level-plus-assignment views. Build a saved view of expiring access cohorts and export it as a renewal outreach list.

 

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