The drag writes the new status to the underlying Everest Forms entry 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 fires exactly as if you had updated the entry from the admin.

Yes. Any dropdown, radio, or checkbox field defined on the Everest 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 statuses.

Entries flagged as spam by the Everest Forms 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.

Yes. Everest Forms stores the final captured values in the same entry row regardless of how the form was laid out, so multi-page and conditional forms appear on the board just like single-page forms. The board reflects only the values the user actually submitted on the form.

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 on the same entries.

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

Yes. The same capabilities that gate the default Everest Forms admin entries screen also gate the SleekView board. A user without permission to view entries cannot see them on the board, and read-only roles get a board they can view but never drag status changes on.

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 delete decisions without polluting your active triage view.