The drag writes the new status to the underlying weForms entry row and fires the standard weForms entry update hook, so the change is real and persistent in the database. Any CRM bridge, ERP integration, or Zapier feed listening on entry updates will fire exactly as if the change had been made from the default weForms entry admin screen.

Yes. Any dropdown, radio, or checkbox field defined on the weForms 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 new, read, and replied states that weForms ships with.

Entries flagged as spam by weForms own anti-spam filters, reCAPTCHA, or honeypot checks 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 any submissions that look like false positives.

Yes. weForms persists every captured value 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 on the card.

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 underlying weForms entries without ever conflicting.

Yes. Any row stored in the weForms entry table appears on the board regardless of how it got there. Entries pushed in through the weForms ERP add-on, the weDevs HRM integration, or any external automation hitting the entry endpoint are indistinguishable from native form submissions as far as SleekView Kanban is concerned.

Yes. The same capabilities that gate the default weForms entries screen also gate the SleekView board. A user who cannot see entries in the standard weForms 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 without extra configuration.

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.