✨ 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 Members: roles & restricted content as tables

Members (the role editor now under MemberPress) writes role-based content restrictions to post meta and capability sets to options. SleekView joins them so each role shows its member roster and every post shows which roles can read it.

♾️ Lifetime License available

SleekView table view for Members

Role rosters and a per-post restriction audit

The Members plugin (originally Justin Tadlock's, now maintained by MemberPress) handles two adjacent jobs. It edits WordPress roles and capabilities, storing the result in the standard wp_options roles record. And it adds Content Permissions, a per-post meta box that lets you restrict a post to one or more roles. Those restrictions live in post meta keys the plugin maintains alongside each post.

The default Members admin gives you a role editor and a capabilities matrix, both well-designed for configuration. What it doesn't give you is a roster — who's on each role, how many posts each role can read, which posts are restricted to which roles. Capability changes are easy, but the operational view of "how does the current capability state map to actual content access for actual users" is missing. Audit work, access reviews, and onboarding sweeps that need to combine the role-side state with the post-side restrictions all sit outside the default UI.

SleekView reads wp_users and the role meta, plus the post-meta keys Members writes for content permissions, and produces two complementary views. A per-role roster shows every member of a role with last login and assigned-on date. A per-post restriction view shows every restricted post with the role list, restriction type, and post status as columns.

Workflow

Roles, members, and restrictions in one workspace

1

Map roles and assignments

Point SleekView at the WordPress roles record and the user-role assignments standard WP maintains. Each role becomes a roster view; each user becomes a row across the roles they hold.
2

Add the restriction view

Read the post-meta keys Members writes for content permissions and produce a per-post restriction view with restricted-to roles, type, and status as columns.
3

Save the audit views

Build saved views for per-role rosters, sensitive multi-role users, posts restricted to deprecated roles, and the recent-restrictions changelog. Gate by role for support, admin, compliance.
4

Edit through standard WP APIs

Role assignments and removals route through add_role() and remove_role() so WordPress hooks fire. Direct meta writes stay available for bulk migrations and one-off cleanups.

Sample columns

A typical Members role roster

Members of a single role with last login and assignment date.
Source: wp_users + wp_options roles + post meta
Member Role Status Last login Assigned Restricted posts
alex@studio.co Subscriber Active Today Jan 12 84
ria@design.io Subscriber Active 2 days ago Feb 03 84
tom@hello.dev Subscriber Inactive 21 days ago Mar 12 84
mia@brew.coop Subscriber Disabled 62 days ago Apr 02 84

Comparison

Default Members admin vs SleekView

Default Members admin

  • Role editor configures roles but doesn't show their rosters
  • Per-post restriction state isn't surfaced as a list view
  • Multi-role users aren't visible at a glance
  • Last-login and capability-state combined need custom queries
  • Access reviews mean role config plus the users screen

SleekView

  • Per-role roster with last login and assigned-on inline
  • Per-post restriction view across the whole site
  • Multi-role users render with all roles concatenated
  • Inline role assignment via the WP user API
  • Save views per role for admin, support, ops

Features

What SleekView gives you for Members

Per-role roster

Build a view per role showing every assigned member with last login and assignment date as columns. The role editor stays where it is for configuration; the roster lives alongside it for ops.

Per-post restriction audit

Build a view of every post with Members content restrictions, showing the restricted-to roles, post type, status, and last edit. Filter to find posts restricted to roles that no longer exist after a role rename.

Multi-role visibility

Users on more than one role render as a single row with all role slugs concatenated. Filter by role to find users holding admin and editor together for sensitive-permission review.

Audience

Who uses SleekView for Members

Compliance and access review

Quarterly reviews of which users hold which roles, which roles overlap, and which posts are restricted to which roles. The roster plus restriction view covers the questions auditors ask.

Support

Per-member role list and last login visible during chat without running queries. Useful for diagnosing "why can't I see this post" tickets where the answer is the per-post restriction state.

Site admins

Bulk role assignment for onboarding cohorts. Per-role audit before deleting a role to confirm no posts still reference it. Restriction sweep before a content migration to ensure permissions move with the posts.

The bigger picture

Why role-based sites need a roster

The Members plugin solves role and capability configuration as well as anything in the WordPress ecosystem. The gap is operational visibility. Once roles are configured and content restrictions are sprinkled across the site, the day-to-day questions stop being about configuration and start being about state.

Who's on each role today? Which posts are restricted to which roles? Which restrictions still point at roles that were renamed last quarter? Which users hold both admin and editor and shouldn't? Members doesn't ship a UI for those questions because they're not configuration questions — they're operational ones. SleekView's roster plus restriction-audit view fills that gap by reading the same data Members already writes and rendering it as columns ops can sort and filter. The role roster is a sort by last login.

The orphan-restriction sweep is a filter on the restriction view. The sensitive-permission audit is a multi-role filter. The configuration stays in the role editor where it belongs; the operational view lives next to it.

Questions

Common questions about SleekView for Members

No. The role editor and capabilities matrix stay where they are for configuration. SleekView adds the roster and restriction-audit views the role editor doesn't surface — who's on each role, what's restricted, and how the two relate.

 

Members writes content-permission settings to post meta keys on each restricted post, including the role list and the restriction type. SleekView reads those keys and renders them as columns in the per-post restriction view.

 

Yes when SleekView routes role assignments through the standard add_role() and remove_role() user methods. Hooks like set_user_role fire so capability sync and integration callbacks run as expected.

 

Yes. SleekView aggregates a user's roles into a single column per row so users on Subscriber and Editor appear once with both roles concatenated. Filter by role slug to find users holding two specific roles together for sensitive-permission audits.

 

Members' Block Permissions feature stores per-block visibility rules in block attributes rather than post meta. SleekView surfaces the post-level restriction state in its restriction view; per-block rules stay in the block editor where they're authored.

 

Members doesn't keep a per-capability change log. SleekView surfaces the current state of roles and restrictions; for a change history, pair it with an activity-log plugin and join the log entries as a related view.

 

Yes. Save a column set per WordPress capability so support, admin, and compliance each see only the columns they need. Per-role views also limit which roles are visible, useful when role configuration is sensitive.

 

Yes. The restriction view queries post meta with the indexed meta_key Members maintains and runs paginated reads. Sites with tens of thousands of restricted posts render the audit view smoothly without scanning the full meta table.

 

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