No. SleekView reads KanbanWP rows live from wp_kanban_tasks on every page load and writes status updates back to the same table. There is no sync job, no second table to keep aligned, and no risk of KanbanWP dashboards going out of step with the kanban view because the source of truth never moves.

Yes. Every drop sends a SQL update to the KanbanWP row that changes the task_status value to the destination lane. Plugin hooks fire as normal so email notifications, role triggers, and analytics events that KanbanWP already runs on status change still fire when the move happens through SleekView.

Yes. Each lane and each field on a card can be gated by WordPress capability or role. Writers might only see their own tasks in the pending and review lanes while admins see every lane including hidden and spam. Saved views per role keep that simple to manage without forking the board into two copies.

SleekView Kanban paginates each lane and lazy loads cards on scroll. In practice a board grouping a hundred thousand KanbanWP rows still opens in under a second because only the visible cards are rendered. Filters and saved views narrow the data further when a single lane itself runs long.

Yes. SleekView checks the same capability that KanbanWP uses before every status write. A reader who cannot edit a task in the KanbanWP admin also cannot drag that card across lanes on the kanban. The board respects every capability check the source plugin already defined so policy stays consistent.

Yes. SleekView does not replace the KanbanWP admin screens. The plugin adds an extra kanban view that points at the same wp_kanban_tasks table. Editors who prefer the original list can keep using it, and any third party plugin that adds columns to the KanbanWP table sees the same data on either surface.

Yes. Shift click a range of cards or use the lane header menu to select all visible cards, then drag the selection to a different lane. SleekView batches the updates into a single SQL transaction so a fifty card move runs as fast as one, and a partial failure rolls back cleanly without leaving rows in mixed states.

SleekView reads the distinct values in task_status every time the board loads, so any new value KanbanWP introduces shows up as a fresh lane automatically. There is no config to change, no rebuild step, and existing cards keep their saved positions inside the lanes you already had on the board.