PublishPress Statuses is the standalone version of the custom statuses feature, available on its own without the rest of the editorial suite. SleekView reads the same post_status values either way, whether they come from the standalone plugin, the bundled module or a hand-rolled register_post_status() call.

Yes. Every registered custom status appears in the status dropdown alongside core values. Pick In Review, Assigned or Pitch and the table narrows in one click.

Yes. Statuses and the calendar are independent layers in PublishPress. SleekView reads the post_status column, which both layers respect, so the calendar and the table stay perfectly in sync without configuration.

With a small audit-log shim, yes. Out of the box, post_status is a current state on wp_posts and SleekView reports the current value plus last modified. For time-in-status, an audit table that logs transitions adds the data needed for a dedicated column.

Yes. Inline edits in SleekView use the standard wp_update_post path, so the same actions, filters and capability checks PublishPress Statuses already hooks fire as expected.

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

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

Yes. Saved views are gated by WordPress capability, so writers can see a scoped view such as their own queue while editors see the full desk. The same view definitions render at the right scope for each role.