Yes. Moving a card calls the ConvertKit API helper that the ConvertKit for WordPress plugin already uses, so confirmations, unsubscribes, and tag updates fire through the normal pipeline. Automations tied to tag changes continue to run, and the WordPress side stays consistent with the audience.

SleekView reads the synced subscriber table that the plugin maintains and joins the form and tag meta in the same query. You pick the synced table as the source, choose the state field to group by, and SleekView renders one card per subscriber with email, tags, source form, and time.

Yes. SleekView ships with role-based permissions, so creators can have a single page that holds the ConvertKit board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role for safer audience review during launches and weekly hygiene rounds.

Pending subscribers land in the Pending column with the time since signup visible. Creators can drag a stalled entry to trigger a resend through the plugin's ConvertKit API helper, and the entry stays in Pending until the subscriber confirms. The Active column updates as ConvertKit confirms.

Each board has one source so the rules stay clear, but the source form filter on the cards lets the same board show every signup form at once. Many creators run one site-wide audience board and a second board scoped to a single campaign form for focused weekly reviews during launches.

Dragging never deletes data outright. It calls the ConvertKit API helper for the matching action, so a card moved to Unsubscribed unsubscribes the subscriber on the ConvertKit side and a bounced card triggers the bounce flow. Only an explicit move into Trash removes the local synced row.

Yes. Each card can show the time since the subscriber signed up or since the last state change, so a pending opt-in that has been waiting for days looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column for stale entries.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the synced subscriber table for the state filter. Sites with very large audiences stay responsive because heavy fields are only fetched for cards currently on screen during a review session.