The drag writes the new status to the underlying HappyForms response row and fires the standard status changed action, so the change is real and persistent. Any Mailchimp tagging, Zapier feed, or custom integration listening on that action will fire exactly as if you had updated the response from the default HappyForms admin screen.

Yes. Any dropdown, radio, or checkbox field defined on the HappyForms 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, in progress, and closed states.

Responses flagged as spam by HappyForms own honeypot or Akismet integration stay flagged on the board. They appear in a dedicated Spam column by default, which keeps the triage lanes clean while still letting an admin scan the spam queue and recover anything that looks like a false positive without leaving the board.

Yes. HappyForms stores the final captured values in the same response 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 board reflects only the values the user actually submitted, conditional fields that were never shown are simply blank on the card.

Yes. Boards are saved as named views and each view can be scoped to specific WordPress roles. A support lead can see a board grouped by ticket status, a marketing user can see one grouped by interest segment, and an admin can see one grouped by spam score, all reading the same underlying HappyForms responses.

Yes. Any row written into the HappyForms response table appears on the board regardless of how it got there. Responses pushed in through the HappyForms REST endpoint or any external automation are indistinguishable from native form submissions as far as SleekView Kanban is concerned.

Yes. The same capabilities that gate the default HappyForms admin screen also gate the SleekView board. A user who cannot see responses in the standard HappyForms 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 responses 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 responses for restore or permanent delete decisions without polluting your active triage view.