Ninja Forms is a little different from most form plugins because it stores submissions as a custom post type called nf_sub, with each field value living as post meta keyed by the field ID. That means submission status is just the standard WordPress post status: publish for received, trash for deleted, and the plugin tracks a custom _seq_num for ordering plus a _status flag for advanced workflows.

SleekView queries wp_posts filtered by post type nf_sub and the form ID in postmeta, then joins on field-ID-keyed meta values for whatever fields you put on the card face. Because the storage is post-meta-based, every dropdown, radio, and checkbox field defined in the form builder is a valid grouping axis. The natural status to group by is the custom _status meta when you use the Submission Status add-on, or any custom dropdown field on the form.

Dragging a card writes back through Ninja Forms own submission update method, which persists the new post meta value and fires the ninja_forms_post_save_sub action so any Zapier feeds, Mailchimp lists, or webhook integrations wired to submission updates run exactly as they would from the admin. Trashed submissions are filtered out by default with a dedicated trash board available.

Ninja Forms gives you a flexible action-based workflow on the form side but its admin assumes you will read submissions one at a time. That assumption holds for a low-volume contact form and breaks down the moment a form becomes part of a real workflow with multiple stages and multiple teammates handling triage in parallel. A kanban board fills the gap directly: queue visibility.

You see at a glance how many submissions are sitting in each stage, which ones have been waiting the longest, and what the team closed since yesterday. Status changes happen with a single drag instead of opening each submission edit screen, which compounds into significant time savings once volume picks up. Because every column maps back to a real field on the submission, the board is not a parallel system that drifts out of sync.

Everything you see is exactly what Zapier, Mailchimp, and your other action-driven integrations already read from the same submission post meta. New teammates onboard in minutes because the board itself documents the workflow visually. The result is a Ninja Forms admin that finally matches how operations and support teams actually run their day-to-day work.