Yes. The board reads the underlying WPForms entries table, and the Form Pages source flag is just one meta value on those entries. You can scope the board to only Form Pages entries with a filter, or include every entry source if you want a single triage view across all of your forms at once.

Yes. The Form Pages source meta records which landing page the lead came through, and SleekView surfaces that meta as a selectable card field. Drop it onto the card front and every card on the board labels its source landing page right next to the lead email and the submission time.

Yes. The drag writes the new triage status value to the entry meta through the standard WPForms entry update path, and the entry update hooks fire so any Zapier zap, CRM sync, or custom integration listening on that hook picks up the change without any extra configuration on your side.

Yes. Boards are saved as named views and each view can be scoped to specific WordPress roles or specific filter sets. A rep assigned to one campaign sees only the leads from that campaign, while the sales lead can see every landing page on a single combined board view for a full overview.

Spam-flagged entries are excluded from every board by default because the spam flag filters them out of the underlying query. You can build a dedicated Spam Review board that flips the filter and surfaces only spam-flagged entries for a quick audit and false positive recovery on a regular basis.

Yes. Any row written into the WPForms entries table appears on the board regardless of how it got there. Zapier-pushed entries, REST API submissions, and standard front-end form submissions all share the same triage status meta and the same lanes when the board reads from the underlying table.

Yes. Every card surfaces a time-in-lane value computed from the last triage status change timestamp stored on the entry meta. Cards that have been sitting in one lane for too long can be filtered to the top, which helps the sales lead spot stalled leads at the weekly pipeline review.

Yes. The same capabilities that gate the default WPForms entries screen also gate the SleekView board. A user without permission to view entries cannot open the board, and read-only roles see a board they can scan but never drag triage updates on, so the security model carries through cleanly.