Yes. Moving a card calls the Hustle module status helpers and the submission lifecycle helpers, the same functions the admin uses, so impression counts, conversion stats, and any custom code listening to Hustle events continue to fire through the normal pipeline without any extra plugin glue or workarounds.

SleekView reads the Hustle module table directly and can also read the submission entries table when the board focuses on hygiene. You pick the source, choose the state field to group by, and SleekView renders one card per module or submission with the fields you select for the card front.

Yes. SleekView ships with role-based permissions, so marketers can have a single page that holds the Hustle board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot promote modules into Active without an approval move.

Custom module types and any extra status values appear automatically because SleekView reads distinct values from the chosen column. You can rename column headers, pick colors, and decide whether marketers can drag cards between any two columns or only along an approved campaign launch path.

Each board has one source so the rules stay clear, but most teams run a modules board for campaign management and a submissions board for audience hygiene on the same dashboard. Column counts at the top of each surface show waiting work at a glance for both.

Dragging never deletes data. It changes the state field SleekView is grouping by, which matches what the admin screens do. Archived modules keep their conversion history and can be reactivated from the same board, and only an explicit move into a Trash column deletes the underlying Hustle row.

Yes. Each card can show the time since the module was paused or last modified, so a module that has been paused for weeks looks visibly different from a fresh pause. Sort options can also place the oldest cards at the top of every column so stale pauses never silently drift out of view.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the Hustle tables for the status filter. Sites with hundreds of thousands of submissions stay responsive because heavy fields are only fetched for cards currently on screen during a review session.