No. SleekView is read/edit only on data that already exists in WordPress. Whether partial submissions are saved depends on Ninja Forms' Multi-Step (or Save Progress) configuration. If the add-on is set to persist partials, SleekView reads them; if not, SleekView shows only completions. Configuration sits in the form settings, not in SleekView.

Whatever the add-on writes. Typical keys include _msf_step (current step), _msf_total_steps (form length), and a last-interaction timestamp. The column picker reads what's in postmeta; if your installation uses different keys (custom code, older versions), they appear under whatever name the add-on wrote.

Not directly. SleekView is a view layer, not a mail-send tool. The supported pattern is to use SleekView's filter to build the list (partials where email was captured), export to CSV, and feed that into your email tool. Alternatively, use a SleekView annotation column to flag rows for a downstream automation to pick up.

If the Multi-Step add-on writes the current step at each transition, yes. If conditional logic skips steps and the meta key reflects the actual displayed step, SleekView shows that. The data is whatever the add-on saved; SleekView's job is to make it visible and groupable, not to reinterpret the saved state.

Save Progress writes partial state to nf_sub as well, often with additional meta indicating resumption tokens. SleekView surfaces those keys too. The combined view is useful: completions, true abandonments, and saved-for-later progressions are visible side by side in one table, distinguishable by their meta keys.

Yes. Filter to abandoned + last-interaction older than 30 (or 60, or 90) days, select all matching rows, and bulk delete. The deletion goes through Ninja Forms' standard nf_sub deletion pipeline, so any registered cleanup hooks fire. Useful for keeping the partials table from accumulating indefinitely.

Step is just an integer in postmeta, so step count itself doesn't affect performance. Where step counts are very long, the column may want a horizontal-progress visual treatment (e.g. "7/12") which SleekView's column formatters support. The funnel report still groups cleanly because each step is a discrete integer value.

Storing partial submissions is your retention decision; SleekView doesn't change it. The data is in wp_postmeta linked to nf_sub rows, so WP's personal-data export and erase tools find it via the standard data-finder hooks. SleekView's filter UI helps locate rows by email when responding to a data-subject request.