The drag writes the new status to the underlying Quform entry row and fires the standard Quform entry update hook, so the change is real and persistent in the database. Any notification, webhook, or integration listening on entry status changes will fire exactly as if the change had been made from the default Quform entry admin screen.

Yes. Any dropdown, radio, or select field defined on the Quform form can be the grouping axis. Most teams add a custom Triage Stage dropdown to the form, flag it as admin-only, and group on that so the board models their actual workflow instead of the default unread, read, and resolved states Quform ships with by default.

Yes. Quform persists the final captured values into the same entry data table regardless of how the form was laid out, so multi-page and conditional forms appear on the board just like any single-page form. The card reflects only the values the user actually submitted, conditional fields that were never shown are simply blank on the card.

Entries flagged as spam by Quform anti-spam features, Akismet, or reCAPTCHA stay flagged on the board. They appear in a dedicated Spam column by default which keeps the triage lanes clean while still giving an admin a place to scan the spam queue and recover anything that looks like a false positive without leaving the board.

Yes. Boards are saved as named views and each view can be scoped to specific WordPress roles. A support lead can keep one board grouped by ticket status, a sales user can keep another grouped by lead stage, and an admin can keep a third grouped by spam score, all reading the same underlying Quform entries without conflicts.

Yes. Any row written into the Quform entry table appears on the board regardless of how it got there. Entries pushed in through the Quform REST endpoint, Zapier, or any external automation are indistinguishable from native form submissions as far as SleekView Kanban is concerned, and they sit in the right column based on their status field.

Yes. The same capabilities that gate the default Quform entries screen also gate the SleekView board. A user who cannot see entries in the standard Quform admin cannot see them on the board, and read-only roles get a board they can view but not drag on, so the Quform security model carries through cleanly without extra configuration.

Trashed Quform entries are filtered out of every board by default because the trash status is excluded from the underlying query. You can build a dedicated Trash review board that flips that filter to surface only trashed entries for restore or permanent delete decisions without polluting the active triage view with deleted records.