Yes. SleekView reads wsf_submit and wsf_submit_meta, both of which exist in LITE. Pro-tier features that store additional data (advanced integrations, custom add-ons) appear automatically if their data is written into wsf_submit_meta as additional meta keys.

Yes. SleekView writes through WS Form's submit update path for supported field types (text, email, number, select, checkbox, date), falling back to direct table writes against wsf_submit_meta with conflict detection on date_updated.

SleekView reads the field configuration from the parent form and joins wsf_submit_meta by submit_id. Each unique field becomes an addable column at query time, so newly added form fields appear immediately.

Yes. Add form_id as a column and filter to a subset of forms or leave it open. Only field keys shared across selected forms become broadly useful columns.

Upload-field meta stores the file URL or attachment ID. SleekView renders these as filename cells linked to the file or media library, and "has attachment" filters on the meta presence.

Yes. The status column on wsf_submit is exposed as a typed column. Inline-edit it row-by-row or in bulk, with WS Form's status hooks firing per row when supported.

When SleekView routes through the submit update path, WS Form's update actions fire per row. Integration actions (Mailchimp, Zapier) are usually configured to run on submission creation, so an inline update may not re-trigger them. Test one row before bulk-applying.

The join between wsf_submit and wsf_submit_meta is paginated server-side. Scope by date range or form_id first to keep the column-chooser inspection fast.