SleekView runs on the child site against the ManageWP worker tables, so any version of the worker that records jobs locally works. Both free and paid ManageWP plans expose the same worker job schema on the child, which means the kanban renders the same way regardless of which network plan you run.

By default a drop only updates the status column. You can extend it with a hook that calls the worker's own retry handler 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 e-commerce sites and another to brochure sites from the same worker log. Each tech 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 the network dashboard reads when it polls the child site, so the network view refreshes on the next sync and never drifts from the live state of the kanban board in front of the tech moving cards.

SleekView respects WordPress capabilities, so you can require manage_options or a custom capability before a card can leave the failed column. Junior techs see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently retrying a 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 in motion.

SleekView reads and writes the existing ManageWP worker tables and never adds shadow tables for job data. View configuration sits in its own small options table, so uninstalling SleekView leaves every job, update, and backup record exactly where the worker wrote it.