Yes. It reads the _form_step meta value that the Multi-Step Forms add-on writes to every submission, joins it to the parent submission row, and renders one column per distinct step. Custom step labels you have configured on the form appear as the column titles automatically.

Yes. When a card moves to a new lane SleekView writes the new step value back through the standard Ninja Forms data layer using the same path the front-end uses. Any submission update hook fires, so Zapier zaps and any custom automation listening for that hook keep working as expected.

Yes. Any meta key on the submission can become the grouping axis. Most teams add a custom triage stage field to the form, expose it only to admins, and group on that so the board reflects how their team actually splits inbound work instead of showing the funnel step.

Spam-marked and trashed submissions are filtered out of every board by default because their submission status excludes them from the query. You can build a dedicated Spam Review board that flips the filter and surfaces only those rows for a quick audit without polluting your active triage view.

Yes. Each distinct step value that actually got reached by at least one visitor becomes a column. A conditional step that only fires for paid plans still gets its own lane, and entries that skipped it never appear on it, so the funnel view stays accurate to what people really walked through.

Yes. Boards are saved as named views and each view is scoped to specific WordPress roles. A support lead can see a board grouped by ticket stage, a sales rep can see one grouped by lead temperature, and an admin can see a board grouped by spam score over the same submissions.

Yes. Any submission written into the Ninja Forms tables appears on the board regardless of how it got there. Entries pushed through the REST endpoint or a custom integration look exactly like submissions made through the front-end form and they share the same step grouping and card fields.

Yes. The same capabilities that gate the default Ninja Forms submissions screen also gate the SleekView board. A user without permission to view submissions cannot see them on the board, and read-only roles see a board they can scan but not drag on, so security carries through cleanly.