Yes. SleekView reads from the same entry storage that free weForms uses, so the free plugin is fully supported. Pro features like advanced fields and integrations add columns to the same storage, so when you upgrade, those columns surface automatically in the table without any additional configuration.

Yes. Pro features like Zapier, Mailchimp, HubSpot, and Salesforce continue to fire because SleekView writes through weForms hooks where applicable. Status changes, entry edits, and bulk actions trigger the same events the native admin triggers, so external systems stay in sync as you triage from the table view.

Yes. File-upload field values appear as links inside the table, so you can preview or download attachments without opening the entry. Useful for application forms where resumes and portfolios attach to each entry, or for support forms where users include screenshots and you need to skim them quickly during triage.

Yes. Multistep entries are stored as one record per submission, so SleekView shows them on a single row with all step fields included as columns. You can filter or sort on any step field, and inline edits work the same as for single-step forms. The multistep UX on the front-end is unchanged.

Yes. Apply filters (cross-form search, status, date range, source page), then export visible rows to CSV with the columns you've configured. Common exports: monthly lead pipeline, event attendee list, candidate shortlist, spam-pattern audit. Filter logic and column choice both persist into the export, so the file is ready to use.

Email notifications already sent stay in inboxes. SleekView only removes the entry from the database, matching weForms' native delete behavior. If you need to recall emails too, that's a function of the email server (Gmail Confidential, similar features) and not something either weForms or SleekView controls.

Yes. Add an Owner column with a user-picker to assign entries to specific team members. Each user can filter to their own assignments to work their queue. Stored as entry metadata, so the data persists even if SleekView is later disabled and you go back to the native weForms admin.

Yes. Fields shown via conditional logic store as the same entry meta as unconditional fields. SleekView includes them as columns where present, and where a field was hidden for a given submission, the cell renders empty. Useful for triaging forms where the visible field set varies by branch (sales vs support, for instance).