It writes. When a card moves from Draft to Scheduled, SleekView updates the sending_type and sending_date columns on the underlying acym_campaign row, so AcyMailing's own cron picks the campaign up on the next tick. There is no separate sync job and no intermediate queue. The card and the campaign row stay in sync because they are the same row.

Use sending_type for the primary lanes, then split Finished out by combining sending_type with the sent flag. That mirrors the four real states AcyMailing tracks: Draft, Scheduled, Sending, and Finished. Some teams add a fifth Paused lane by reading the active column. SleekView lets you compose the group-by from multiple columns in the view config.

Yes. Add a recipient list filter to the kanban view and the board only shows campaigns targeting that list. Save the filtered view as its own URL, share it with the lifecycle or product team, and they each get a focused board. The underlying AcyMailing campaigns stay in the same tables, just rendered through different SleekView views.

Nothing, if you set permissions correctly. SleekView respects native WordPress capabilities, so only roles with the publish-equivalent capability can drop a card into a live send lane. For writers the lane becomes a non-drop target and the card snaps back. You can also require a confirmation modal for that specific lane in the view settings.

No. SleekView only writes the same columns AcyMailing already updates from its own UI, so opens, clicks, bounces, and unsubscribes continue to record exactly as before. The reporting tables AcyMailing maintains are untouched, and the campaign detail page inside AcyMailing keeps showing the same metrics it always did.

The kanban collapses into a vertical stack of lanes on screens narrower than the breakpoint you choose. Each lane shows the same card front, and tapping a card opens the detail sheet. Drag-and-drop works on touch the same way it works with a mouse, so a quick pipeline change from a phone is one swipe and a confirm tap.

Yes. SleekView reads anything you can put in a SQL view, so you can join the AcyMailing campaign table to a custom approvals table or a postmeta key that stores the assigned editor. The joined columns become available as card fields without changing the AcyMailing plugin or its database. Updates to those custom fields can also be written back.

No. SleekView paginates each lane independently and only loads card data for the lanes currently in view. Finished can hold tens of thousands of rows because the lane lazy-loads as you scroll. The active lanes that actually need real-time accuracy stay snappy because they only carry the small number of in-flight campaigns.