Yes. SleekView queries the Spin Rewriter job table directly, so the rows on the kanban are the rows on the plugin dashboard. A job queued five seconds ago appears on the next board refresh without any sync step, and a completed job moves out of Generating immediately.

Yes. Every drag fires a safe update on the primary key of the Spin Rewriter row, writing the new status in place. Approval automations that watch the status column run on the next cycle, so a kanban drag is enough to trigger downstream publishing.

Yes. Filters apply on top of the kanban grouping. Pick the source post type you want and the board shows only those jobs, while still grouping them by status. Save the filter and the team opens a board specific to their slice of the queue.

SleekView renders one column per distinct value it finds in the grouping field. Custom statuses like Needs legal sign off appear automatically as new columns the next time the board loads, so the kanban tracks the workflow your team uses, not a generic default.

Yes. The card editor lets you pick a title field plus a single meta line that combines multiple Spin Rewriter columns. A common setup shows the source post title as the card title and a meta line like 3 variants, target product, editor Lena.

Yes. SleekView paginates inside each column, so even a board with twenty thousand approved rewrites loads in well under a second. Drags fire one indexed update on the primary key, so the kanban stays responsive on busy publishing days.

Yes. SleekView inherits the capability you configure on the view. A contributor role can be limited to viewing, an editor role can move cards between draft and review columns, and an administrator role can move cards into Approved or Published.

Nothing happens to them. SleekView never owns Spin Rewriter data, it reads and updates the plugin's own rows in place. Deactivating SleekView only removes the kanban view, not the rewrite history, so Spin Rewriter keeps queuing and storing jobs exactly as before.