SleekView for PressPermit
SleekView reads the wp_ppc tables that PressPermit writes and turns every legacy exception into a sortable, filterable, inline-editable row, including the migration tags you need for PublishPress Permissions.
♾️ Lifetime License available
PressPermit was powerful, but the admin is dated
PressPermit was the first serious permission layer for WordPress and it shaped what PublishPress Permissions later became. Sites that adopted it years ago accumulated hundreds of exceptions across roles, posts and terms. The legacy admin spreads those rules across narrow per-post and per-role screens, which made sense in 2014 but makes auditing in 2026 painful. Without a flat list, the only way to see what the legacy install enforces is a SQL query and a lot of squinting.
SleekView reads the wp_ppc_exceptions and wp_ppc_exception_items tables PressPermit writes and joins them with role, item and operation references. Every legacy exception becomes a row with the same shape as a PublishPress Permissions row, which makes a side-by-side migration analysis straightforward. Sort by role to see every grant given to subscribers. Filter to operation equals read and item type equals term to confirm which restricted libraries are still locked down. Tag rules for keep, deprecate or rewrite as part of a documented migration plan.
The view is read-write where it makes sense: operation, role and status can be edited inline through the legacy API. Bulk migration moves still flow through PublishPress's official import paths. SleekView's job is to make the audit possible at all.
Workflow
Audit a legacy PressPermit install before you migrate
Read legacy schema
Tag for migration
Spot duplicates
Export the plan
Sample columns
PressPermit rule ledger
wp_ppc_exceptions
| Item | Type | Operation | Role | Updated | State |
|---|---|---|---|---|---|
| Internal Wiki | Term | Read | Editor | 2025-12-10 | Active |
| Legacy Promo | Post | Edit | Author | 2024-07-22 | Review |
| Old Restricted | Term | Read | Subscriber | 2023-08-04 | Stale |
| Press Releases | Post | Edit | Editor | 2026-04-12 | Active |
Comparison
PressPermit admin vs SleekView
PressPermit admin
- Legacy admin is split across many narrow screens
- No combined sort by role and operation
- Filtering across exception types is limited
- Bulk edit of operations is not exposed
- Hard to plan a migration without a flat list
SleekView
- One table for every legacy PressPermit exception
- Filter by role, operation and item type
- Sort by role, item and last update
- Inline edit operation, role and status
- Export the full rule ledger as CSV for migration
Features
What SleekView gives you for PressPermit
Legacy ledger
Every PressPermit rule joined from wp_ppc_exceptions and wp_ppc_exception_items in one table so you can finally see what the legacy install actually enforces.
Find conflicts
Filter by role and item to spot allow and block rules colliding on the same content, the most common source of mysterious access bugs after years of edits.
Migration plan
Tag rules to keep, deprecate or rewrite when moving to PublishPress Permissions, so the audit becomes the migration plan instead of a separate document.
Audience
What PressPermit teams use SleekView for
Compliance reviews
Export the rule ledger to share with security and confirm exactly who can do what before the auditor's annual visit, without writing custom SQL.
Migration planning
Decide which legacy PressPermit rules survive the move to PublishPress Permissions and which are obsolete artefacts of campaigns long ended.
Conflict cleanup
Sort by item to find duplicate or contradicting rules ready to be merged, removing audit-confusing noise before the new system inherits it.
The bigger picture
Why a legacy PressPermit audit cannot be skipped
PressPermit installs that have run for years usually carry rules nobody on the current team wrote. A legal team requested a restriction in 2018, a freelancer added a guest grant in 2021, an editor created a category-level allow rule for a campaign that ended a long time ago. Every one of those rules still enforces, and the legacy admin makes them genuinely hard to find.
Migrating to PublishPress Permissions without auditing first means importing the noise alongside the signal and inheriting the same audit problem in a fresher schema. The flat ledger view changes the migration economics. Sorting by role surfaces who has access to what.
Sorting by item surfaces collisions. Tagging rows turns the audit into a working document. Once the team has decided which rules survive, the migration into PublishPress Permissions becomes a clean event rather than a forklift of mystery data, and the new system starts with a clear conscience instead of a debt.
Questions
Common questions about SleekView for PressPermit
Yes. The schema PressPermit writes is the direct ancestor of the PublishPress Permissions schema, and SleekView reads both. The PressPermit view focuses specifically on the legacy column layout and the rule shapes that pre-date the PublishPress rebrand, so older installs work without forcing an upgrade first.
Most teams should, eventually. PublishPress Permissions is actively maintained, supports newer WordPress capabilities and integrates with the rest of the PublishPress suite. SleekView makes the audit easier so the migration is a thoughtful event with a clear plan rather than a forced upgrade carrying mystery rules forward.
Yes. Inline edits go through the same PressPermit API hooks the legacy admin uses, so caches refresh, capability filters fire and the next request sees the new rule. The view never writes directly to wp_ppc tables, which keeps the legacy install consistent.
Yes. Any filtered or tagged view can be exported as CSV with the columns and order you see on screen. The export is the typical artefact migration teams hand to security, and the format matches the PublishPress Permissions export so the same spreadsheet can be reused after the move.
Super admins still bypass rules at the PressPermit layer, and SleekView never overrides that. The table reflects what is stored, not what is enforced for super admins. Effective access is determined by PressPermit's resolution logic, which the view does not change in any way.
Custom operations registered with PressPermit appear as values in the operation column you can sort and filter. If your legacy install added a custom capability for an editorial workflow, every rule referencing it shows up under that operation value with the same precision as a built-in one.
Yes. Joining through the users table makes rules that reference deleted accounts visible as rows with an empty user reference. Those are usually the cheapest cleanup wins on a legacy install, since they enforce nothing useful and clutter the audit.
PublishPress recommends migrating fully rather than running both. SleekView supports each in its own view so you can audit one before the move and verify the result in the other afterwards, but enforcement should always sit with one plugin to avoid contradictory cache states.
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