Directly from wp_posts (for custom post_status values), wp_postmeta (for editorial metadata such as owner, deadline and slot) and the PublishPress editorial comments table. No exports, shadow copies or extra plugins are involved.

Yes. Custom statuses live in the post_status column on wp_posts after PublishPress registers them, so they become a dropdown filter with the full list of registered statuses alongside core values like draft and pending.

Yes. The PublishPress editorial comments table joins on post id, so the count renders as a sortable column. A simple click pulls the posts that triggered the most review traffic to the top of the table.

Yes. Pro features such as additional metadata, content checklists and editorial reminders extend the data PublishPress writes to postmeta. SleekView reads those keys the same way it reads the free plugin's, so Pro-only fields become extra columns.

Inline edits in SleekView route through the standard wp_update_post path, the same one PublishPress hooks listen to. Status changes, owner updates and deadline edits fire the same actions as saving the metabox, so workflow notifications continue firing.

Yes. Add a filter for category, custom taxonomy or post type and the whole table narrows to that section. Desks running separate sections such as news, features and opinion each get their own scoped audit.

Queries hit indexed columns on wp_posts (post_type, post_status, post_modified) and the indexed meta_key column on wp_postmeta. Filters compose into a single SQL query, so even desks with thousands of in-flight posts render fast.

No. PublishPress still owns the calendar, the metabox and the comments thread. SleekView adds a sortable cross-post table that complements the calendar with the kind of list-and-filter surface a calendar grid is not designed to provide.