The drag writes the new status to the underlying Kali Forms entry row and fires the standard Kali Forms entry update hook, so the change is real and persistent. Any Mailchimp sync, Zapier feed, or webhook listening on entry status changes will fire exactly as if the change had been made from the default Kali Forms entry admin screen.

Yes. Any dropdown, radio, or checkbox field defined on the Kali Forms 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 starred states Kali Forms ships with.

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

Entries flagged as spam by Kali Forms own anti-spam filters, reCAPTCHA, or honeypot checks stay flagged on the board. They appear in a dedicated Spam lane by default, which keeps the triage columns clean while still giving an admin a place to scan the spam queue and recover any submissions that look like a false positive.

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 marketing user can keep another grouped by interest segment, and an admin can keep a third grouped by spam score, all reading the same Kali Forms entries.

Yes. Any row written into the Kali Forms entry table appears on the board regardless of how it got there. Entries pushed in through the Kali Forms 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 Kali Forms entries screen also gate the SleekView board. A user who cannot see entries in the standard Kali Forms admin cannot see them on the board, and read-only roles get a board they can view but not drag on, so the security model carries through cleanly.

Trashed 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.