SleekView reads PublishPress Future data directly from the WordPress database, so any version that writes to the Action Scheduler tables works. Both the free core and the Pro license expose the same schedule schema, which means the kanban renders the same way regardless of which PublishPress Future plan you run.

By default a drop only updates the status column. You can extend it with a hook that calls the Action Scheduler retry helper when a card leaves the failed lane, and that is exactly how most teams wire it up. SleekView keeps the two actions separate so accidental drags never trigger a retry storm.

Yes. SleekView views are configuration only, so you can build one board filtered to unpublish actions and another to delete actions from the same Action Scheduler tables. Each editor picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole team.

SleekView reads distinct status values on every load, so a new status shows up automatically as its own lane at the end of the board. You can drag it into the right position in the pipeline, assign a color, and decide which fields the lane's cards should surface, without rebuilding the view.

No. The drag handler updates the same status column that Action Scheduler reads on every cron tick, so the next run picks up the new state exactly as it would if a developer updated the status from WP-CLI, and the queue continues processing without interruption.

SleekView respects WordPress capabilities, so you can require manage_options or a custom capability before a card can leave the failed column. Editors see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently retrying a broken job.

Each lane uses a virtual scroller, so a column with thousands of cards still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top of the board narrows large lanes without resetting the scroll position or any cards already in motion.

SleekView reads and writes the existing Action Scheduler tables that PublishPress Future uses and never adds shadow tables for action data. View configuration sits in its own small options table, so uninstalling SleekView leaves every scheduled action exactly where PublishPress Future and Action Scheduler wrote it.