SleekView for PublishPress Permissions
SleekView joins wp_ppc_exceptions with wp_ppc_exception_items and the role and item references so every PublishPress Permissions rule shows up as one filterable, inline-editable row.
♾️ Lifetime License available
Permissions rules pile up faster than you can audit them
PublishPress Permissions is the most flexible role and capability layer for WordPress, but its admin is built around the post or term you are editing right now. Each exception lives next to the content it qualifies, and the role-side screens show grants per role rather than per item. After a few months of editorial work the rules pile up across categories, custom post types and individual posts, and the only way to see them together is a custom SQL query against the wp_ppc tables.
SleekView reads wp_ppc_exceptions, wp_ppc_exception_items and the linked term and post rows in one query. Every exception becomes a row with item, item type, operation, role, status and last update. Filter to a single role to see every grant and block touching that team. Sort by item to spot a single category wrapped in three contradictory rules. Filter to operation equals edit and status equals block to confirm no editor has been quietly locked out of a content area.
Inline edits run through the standard PublishPress Permissions API, so caching, capability hooks and any custom enforcement code keep working. The plugin still owns the security model. SleekView is the audit and triage surface that turns hundreds of scattered rules into something a security review can actually consume.
Workflow
Turn permission rules into a single audit ledger
Read the schema
Filter by role or item
Spot collisions
Edit and export
Sample columns
Permissions exception ledger
wp_ppc_exceptions
| Item | Type | Operation | Role | Status | State |
|---|---|---|---|---|---|
| Editorial 2026 | Term | Edit | Editor | Allow | Active |
| Old Campaign | Post | Read | Subscriber | Allow | Review |
| Internal Docs | Term | Edit | Author | Block | Restricted |
| Press Releases | Post | Edit | Editor | Allow | Active |
Comparison
PublishPress Permissions admin vs SleekView
PublishPress Permissions admin
- Exceptions are split across post and role screens
- No combined sort by role and operation
- Filtering across types is limited
- Bulk edit of operations is not exposed
- Hard to spot conflicting allow and block rules
SleekView
- Joins wp_ppc_exceptions and wp_ppc_exception_items in one table
- Filter by role, operation and exception type
- Sort by role, item type and last update
- Inline edit operation, status and applies-to
- Spot conflicting allow and block rules at a glance
Features
What SleekView gives you for PublishPress Permissions
Rule ledger
Every exception in wp_ppc_exceptions joined with role, item type, operation and status, so an entire site's permission model fits in one sortable table.
Find conflicts fast
Filter by role and item to surface posts wrapped in colliding allow and block exceptions, the leading cause of confused editor experiences.
Inline rule edits
Toggle operation, change the assigned role and update status from the row while PublishPress Permissions still fires its cache and capability hooks.
Audience
What Permissions teams use SleekView for
Quarterly access audits
Filter by role, sort by last update and export the rule ledger as CSV so security and compliance can sign off on access in a single review.
Onboarding new roles
Group exceptions by role and item type to plan grants and blocks for a new editor or external contributor team before they ever log in.
Conflict cleanup
Sort by item to find a single post or term wrapped in conflicting allow and block rules and resolve the contradiction inline in seconds.
The bigger picture
Why scattered permissions become real risk
PublishPress Permissions is usually adopted because the default WordPress role system is too blunt: editors should not see embargoed campaigns, contractors should only edit their own taxonomies, an external agency should not approach legal pages. Those decisions are right, but they generate hundreds of small exceptions that are hard to remember six months later. The risk is not a single broken rule, it is the accumulated drift: a former employee whose role was deleted but whose exceptions remain, a category created last year with allow exceptions that nobody reassessed, a post type rolled out with default rules that turned out to be too permissive.
Without a flat ledger, audits get reduced to spot checks, which leak access by omission. A real list view turns a security review from an exercise in memory into a sortable spreadsheet that two reviewers can scan together. That difference is what keeps an enterprise PublishPress install actually enforceable rather than only enforced.
Questions
Common questions about SleekView for PublishPress Permissions
No. PublishPress Permissions still owns enforcement, capability resolution and any custom logic registered through its filters. SleekView is a faster audit and triage surface for the same data, designed for the moments where the per-post UI breaks down: cross-site reviews, role offboarding and conflict cleanup.
From wp_ppc_exceptions and wp_ppc_exception_items, the canonical tables PublishPress Permissions writes to. SleekView joins those with the standard posts, terms and users tables so each exception shows the role, item, item type and operation it targets without needing a custom SQL view.
Yes. Edits run through the standard PublishPress Permissions API rather than direct table writes, so any cache invalidation, capability filters or custom enforcement plugins fire as if the change had been made through the per-post UI. The next request sees the new state.
Yes. Any filtered view can be exported as CSV with the columns and order you see on screen. Most security teams use this to bundle quarterly reviews into a single attachment for compliance, with role, operation and item type as the canonical sort.
PressPermit is the legacy version that PublishPress Permissions descended from. The schema is similar, and SleekView has a separate page for PressPermit installs. This page focuses on the current PublishPress Permissions schema, including its newer columns for status and applies-to.
Super admins always bypass the rules in PublishPress Permissions, and SleekView never overrides that. The table reflects the data exactly as stored, so super admins still appear in role columns where applicable but their effective access is determined by the plugin, not the view.
Yes. Because SleekView joins through the users table, exceptions that reference deleted accounts surface with an empty user reference, making them easy to filter and clean up. This is the cheapest way to spot lingering grants left behind after offboarding.
Yes. PublishPress Permissions supports custom post types and custom taxonomies as exception targets, and SleekView treats those as values in the item type column. A site with a private docs CPT or a partner-only taxonomy can filter to that one item type and review every rule touching it.
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