Yes for the full feature set. The free Everest Forms plugin stores entries in everest_forms_entries and everest_forms_entrymeta too, but several Pro add-ons (Multi-Part Forms, Conversational Forms, Payments) add meta keys that SleekView surfaces as columns. The Pro license is what unlocks those extra fields on the source side.

Yes. SleekView writes back through Everest Forms' entry-update API where the field type supports it, so validation and registered hooks behave the same as a normal entry edit. For low-level fields the API does not expose, direct updates to everest_forms_entrymeta happen with conflict detection.

SleekView reads the unique meta_key values in everest_forms_entrymeta for entries in the selected scope and exposes each as an addable column. The pivot runs at query time using a join, so new form fields surface immediately as the column picker rescans.

Yes. Add form_id as a column, then either filter on a subset of forms or leave it open for a unified inbox. For cross-form views, only meta keys present on multiple forms become useful columns; SleekView shows which keys belong to which form so column choices stay sensible.

Yes. Payment-related fields write to everest_forms_entrymeta like other field types, so payment status, gateway, and amount appear as pivotable columns. Reconciliation views with amount and date filters fall out of the same engine, no special handling required.

Yes. Save views and scope them per WordPress role or capability. Sales sees a cross-form unread inbox, support sees a starred-and-open view, moderation sees a spam queue. Views are config artefacts and can be versioned in your codebase if you prefer infrastructure-as-code.

Everest Forms stores entry notes inline with the entry detail rather than as a separate first-class table for all versions. Where the notes data is available, SleekView exposes it as a related view with note count as a column and the thread visible on row expansion. Where it is not, the row-detail panel still surfaces the data the API returns.

Bulk delete from a SleekView row routes through the Everest Forms admin API so its standard deletion hooks fire, including any cleanup logic registered by add-ons. A filtered view for a single email address makes data-subject access requests a two-click export plus a one-click bulk delete.