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 the statuses come from the standalone plugin, the bundled module or a hand-rolled register_post_status() call.

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 chart dashboard stay perfectly in sync without configuration.

Yes. Filter to a single post_status, group by post_modified or post_date with an Area or Line card and pick a Count aggregation. The trend is the cleanest way to see whether a particular bucket, such as In Review, is growing or being drained week by week.

With a small audit-log shim, yes. Out of the box, post_status is a current state on wp_posts and SleekView reports current counts. For time-in-status, an audit table that logs transitions adds the data needed for an Average duration card per status.

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

Yes. Inline edits from the underlying SleekView table use the standard wp_update_post path, so the same actions, filters and capability checks PublishPress Statuses already hooks fire as expected. Custom statuses behave identically whether the change comes from the editor or the table view.

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

Yes. Any filtered set behind a chart card exports as CSV with the underlying posts, statuses and editorial metadata. Managing editors typically use this for weekly reports to publishers or to brief freelance editors on the backlog before a sprint.