✨ 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 Kanban for Members

The Members plugin restricts content by role and stores that restriction as postmeta on every protected post. SleekView Kanban reads those posts, groups them by the role allowed to read them, and lets an editor drag a card to change the access role from one screen.

♾️ Lifetime License available

SleekView Kanban board for Members

Read Members-restricted content as a board, not a list

The Members plugin, by MemberPress, manages roles and capabilities and adds per-post content restriction through a metabox on the post edit screen. The restriction is stored as postmeta with the key _members_access_role, holding one or more role slugs that are allowed to read the post. Public posts have no meta, restricted posts carry a value such as subscriber, contributor, premium_member, or editor.

SleekView reads the standard wp_posts table joined to the _members_access_role postmeta and treats the access role as the natural column to group by. Public, Subscribers only, Members only, and Editors only appear as their own columns with their actual counts. Post title and type ride on the card front, with author and last modified date on a second line so an editor reads the access map of the site without opening individual posts.

Drag a card from Public to Members only to restrict access and SleekView writes the corresponding _members_access_role postmeta through the standard WordPress update path, so the Members plugin's restriction rules apply on the next page load exactly as if the change had been made on the post edit screen. Filters scope the board to one post type when the site mixes posts, pages, and custom types.

Workflow

From _members_access_role meta to an access board

1

Connect SleekView to the Members data

Add a SleekView data source pointed at wp_posts joined to the _members_access_role postmeta. SleekView reads the schema and offers the access role meta as the obvious column to group by.
2

Pick access role as the column

Choose the access role meta as the kanban column. SleekView builds one column per real role value the meta contains, plus a Public column for posts with no restriction. Each column shows its actual count at the top.
3

Choose what shows on each card

Pick the fields that ride on the card front. Post title and post type come first, with author and last modified date on a second line so an editor reads the access map without opening each post.
4

Enable drag and drop with confirmation

Turn on drag and drop. Moving a card from Public to Members only writes the _members_access_role meta through the standard WordPress update path, and the Members plugin's restriction rules apply on the next page load.

Sample board

Sample Members access board

Four real access groupings with three cards each, showing post title, type, author, and last modified so an editor reads the access map cleanly.
Public
412
How we shipped the new dashboard
Post by Jordan, modified 02 Jun
Pricing FAQ
Page by Sara, modified 18 May
Open source roadmap update
Post by Mira, modified 11 May
Subscribers only
87
Weekly subscriber digest 22
Post by Newsletter, modified 06 Jun
Reader-only Q and A archive
Page by Sara, modified 28 May
Subscriber thank-you note
Page by Jordan, modified 14 Apr
Members only
143
Members deep dive on caching
Post by Mira, modified 04 Jun
Members workshop replay archive
Page by Jordan, modified 22 May
Members starter kit downloads
Page by Sara, modified 09 May
Editors only
18
Internal style guide
Page by Editor, modified 30 May
Editorial calendar Q3
Page by Editor, modified 27 May
Pre-publish review checklist
Page by Editor, modified 13 May

Comparison

Default Members admin vs SleekView Kanban

Default Members content audit

  • Members sets restriction on the post edit screen with no overview of the whole site by role
  • Auditing the access map means opening every post or running a custom postmeta query
  • No card layout that puts post title, type, author, and last modified together by access role
  • No saved board view for editors who manage the access map across many post types
  • No frontend embed for a stakeholder reviewing what is public versus members-only

SleekView Kanban

  • Cards built from wp_posts joined to the _members_access_role postmeta
  • Group by the real access role with Public, Subscribers only, Members only, and any custom role
  • Drag a card to write the access role meta through the standard WordPress update path
  • Save board views per editor or post type with scoped filters and card fields
  • Embed any saved board on a frontend page with role-based access for reviewers

Features

What SleekView Kanban gives you for Members

A real access map as a board

SleekView reads wp_posts joined to the _members_access_role meta and shows each post as a card grouped by access role. Title, type, author, and last modified ride on the card front so the access map of the site is one screen.

Drag and drop that writes meta

Moving a card from Public to Members only writes the _members_access_role postmeta through the standard WordPress update path, and the Members plugin's restriction rules apply on the next page load exactly as on the post edit screen.

Scoped by post type

Each saved board view can be scoped to a single post type or a single access role, so an editor working only on pages saves one board, and another editor working only on a custom resources type saves a different board.

Audience

Who runs a Members access board

Editorial leads

Audit the access map of the site in one screen, drag posts that should be Members only out of the Public column, and keep the editorial calendar honest about what is gated.

Site administrators

Save a board scoped to custom post types to confirm that internal documentation is restricted to Editors only and never accidentally exposed to the public column.

Membership owners

See the count of Members only posts grow across the year as a leading indicator of the value the membership tier delivers, without exporting a custom report.

The bigger picture

Access decisions live on posts, so audit them as a board

The Members plugin decides who can read a post through role-based capabilities and per-post overrides stored in postmeta. The plugin is excellent at the writing side: roles are easy to define, capabilities are easy to assign, and the per-post metabox is right there on the edit screen. The reading side, though, depends on opening individual posts or running custom queries, which makes auditing the access map of a site hard.

SleekView Kanban reads the same posts and meta and groups by access role, so Public, Subscribers only, Members only, and any custom role appear as columns with their counts. Editorial leads audit the map in one screen, drag posts that should be gated out of Public, and keep the editorial calendar honest. Membership owners watch the Members only column grow as a leading indicator.

The Members plugin still owns role definitions and capability enforcement, only the way the team audits and adjusts the map changes.

Questions

Common questions about SleekView Kanban for Members

No. The Members plugin still owns role and capability definitions and per-post restriction enforcement. SleekView Kanban is a reading and dragging layer on top of the _members_access_role postmeta, useful when an editor needs to audit the whole access map at once instead of opening posts one at a time.

 

Whatever role slugs the _members_access_role postmeta contains, plus a Public column for posts with no restriction. Built-in roles such as subscriber, contributor, and editor appear when they are used, and any custom role defined through the Members plugin appears as soon as a post carries it.

 

SleekView writes the _members_access_role postmeta through the standard WordPress update path. The Members plugin's restriction rules apply on the next page load exactly as if the change had been made on the post edit screen, including any caching invalidation the site does.

 

Yes. SleekView saves filters per board view, so an editor working only on pages can save a board scoped to pages while another editor working on a custom resources type saves a different board. Each view stays scoped to the user who saved it.

 

Yes. A post can carry more than one access role in the meta. SleekView shows that post as a card in each matching column with a small indicator that the post is restricted to multiple roles, so the editor sees the full picture without ambiguity.

 

Yes. SleekView refreshes on a short interval and on focus, so two editors working at once see each other's drag results within a few seconds. The underlying data is the same wp_posts and postmeta, so there is no separate state to reconcile.

 

It applies the same restriction the Members plugin would apply on the post edit screen. Whether the post is hidden from search results depends on the plugin's settings and any theme-level handling, the board does not introduce a different rule.

 

Yes. Save a board view, then embed it on a private frontend page reachable only by users in the right role. Reviewers read the access map without a full WordPress admin login, protected by the standard WordPress capabilities Members defines.

 

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