SleekView reads Automator data directly from the WordPress database, so any version that writes to the recipe log table works. Both the free build and the Pro license expose the same log schema, which means the kanban renders the same way regardless of which Automator plan you run.

By default a drop only updates the status column. You can extend it with a hook that calls Automator's own retry helper when a card leaves the errored lane, and that is exactly how most teams wire it up. SleekView keeps the two actions separate so accidental drags never trigger a flood of retries.

Yes. SleekView views are configuration only, so you can build one board filtered to onboarding recipes and another to CRM sync recipes from the same Automator log. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole ops 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 completion status column that Automator reporting reads, so widgets refresh on the next page load and never drift from the live state of the kanban board in front of the admin moving cards.

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

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 Automator recipe log tables and never adds shadow tables for run data. View configuration sits in its own small options table, so uninstalling SleekView leaves every recipe, run, and reporting widget exactly where Automator wrote it.