SleekView Kanban for WS Form LITE
SleekView reads WS Form LITE submissions straight from the submission tables, groups them by submission status or any field on the form, and lets your team drag cards across columns to advance review without leaving WordPress or opening every record one by one.
♾️ Lifetime License available
Why WS Form LITE submissions need a board
WS Form LITE is the free version of the popular Westguard Solutions form builder. Submissions land under WS Form > Submit as a paginated table with the form, the submitter, the submission date, and the built-in status column. That is enough for low-volume contact forms, but the moment a WS Form is wired into a real workflow like quote requests, applications, or onboarding intakes, the flat list stops being useful as an operations dashboard.
SleekView reads from wp_wsf_submit and wp_wsf_submit_meta where WS Form persists every submission. The built-in status column is the natural grouping axis, the same column WS Form toggles between draft, publish, pending, and trash as the submission moves through its lifecycle. Each card shows submitter name, the first non-empty field on the form, a relative timestamp, and the form title when the board spans multiple forms.
Dragging a card from one column to another writes the new status back to the same row through the WS Form submission API, so any actions or webhooks WS Form fires on submission status changes keep working exactly as before. Spam and trashed submissions are filtered out of every board by default, but a dedicated review board can flip those filters back on for admin clean-up sessions.
Workflow
From WS Form submission list to a real board
Connect a WS Form
Pick the grouping column
Pick card face fields
Enable drag-and-drop write-back
Sample board
Sample WS Form LITE submission board
Comparison
Default WS Form submission list versus SleekView Kanban
Default WS Form submissions
- Submissions land in a paginated list with no visual sense of queue depth or progress
- Status changes require opening every submission individually, no drag between columns
- Custom field grouping is not available, the submission list always sorts by date order
- Assignee tracking lives in form fields with no per-card visual cue from the overview
- Team handoffs depend on the notes field which is hidden from the submission list view
SleekView Kanban
-
Reads directly from
wp_wsf_submitand submit_meta with no duplicate storage - Drag-and-drop writes back via the WS Form submission API so WS Form actions still fire
-
Group by built-in
statusor any custom field on the WS Form definition - Card face accepts up to six fields including calculated and hidden admin fields
- Works alongside WS Form actions, webhooks, and Zapier without extra configuration
Features
What SleekView Kanban gives you for WS Form LITE
Group by any field on the form
Built-in submission status is the default grouping but any dropdown, radio, or select field becomes a column axis. Boards remember the grouping per user so different teammates can scan the same WS Form submissions through their own operational lens without ever competing for one shared layout in the WordPress admin.
Drag-and-drop updates the submission
Moving a card calls the WS Form submission API, which fires the standard WS Form actions so any webhook, integration, or follow-up action listening on submission status changes stays in sync. The UI updates optimistically and rolls back gracefully if the underlying API write returns an error.
Per-role column visibility
Hide the Trash lane from junior reps, hide the Published lane from active triage, or expose hidden calculated fields only to managers. Permission rules read from the standard WordPress role and capability map you already configured, so new teammates inherit the right board view from their assigned role with no extra setup.
Audience
Common WS Form LITE boards teams build
Quote request pipeline
Group quote requests by approval stage so the sales team knows which quotes are pending review, which are approved, and which got accepted by the client without leaving the WordPress admin.
Application review
Group inbound applications by recruiter stage so hiring managers can see who is in screening, who is in interview rounds, and who needs an offer letter sent without scrolling through the full submission list.
Onboarding intake tracking
Group onboarding intake submissions by completion stage so the success team knows whose paperwork is in, whose is pending an upload, and whose is ready for the next call.
The bigger picture
Why a board beats a WS Form submission list
WS Form LITE is a powerful form builder with conditional logic, calculations, and a clean admin pattern, but that admin pattern was designed for collecting data, not for running operational triage on it. The default submissions screen treats every record as just one row in a list, the same way the orders screen treats orders. That is fine for a contact form pulling in a handful of messages a week.
It collapses the moment a WS Form is doing real operational work like quote intake, applications, or multi-stage onboarding, because the list view tells you nothing useful about queue depth, ownership, or what got cleared since yesterday. A kanban board fixes the visibility gap by turning the most important field into a set of columns and every submission into a card with the right summary on its face. You see in one glance how many submissions are still in draft, how many are pending approval, and how much got published since the start of the week.
Status changes happen with a single drag instead of three clicks per record, which compounds into real time savings every day. And because the board reads and writes the same underlying WS Form tables, nothing drifts. Actions fire, webhooks deliver, and the team finally has an operational surface that matches how the work actually flows.
Questions
Common questions about SleekView Kanban for WS Form LITE
The drag writes the new submission status to the underlying WS Form submission row through the WS Form submission API, so the change is real and persistent. Any WS Form action, webhook, or follow-up integration listening on submission status changes fires exactly as if the change had been made from the default WS Form submission screen.
Yes. Any dropdown, radio, or select field defined on the WS Form can be the grouping axis. Most teams add a custom Triage Stage select to the form, flag it as admin-only, and group on that so the board models their actual workflow instead of the default draft, pending, and publish states that WS Form ships with out of the box.
Yes. WS Form persists the final captured values along with calculated field results into the submission meta table, so conditional and calculated fields appear on the board just like any other field. The card reflects only the values actually present on the submission, conditional fields that never displayed during the submit flow are simply blank.
Draft submissions appear in a dedicated Draft column by default, since WS Form supports a save and resume flow that creates rows before the form is fully submitted. That keeps active in-progress submissions visible without polluting the live triage lanes, and you can drag a card from Draft to Pending once it is ready for review.
Yes. Boards are saved as named views and each view can be scoped to specific WordPress roles. A sales lead can keep one board grouped by quote stage, a recruiter can keep another grouped by application stage, and an admin can keep a third grouped by status, all reading the same underlying WS Form submissions without conflicting with each other.
Yes. Any row written into the WS Form submission table appears on the board regardless of how it got there. Submissions pushed in through the WS Form REST endpoint or any external automation are indistinguishable from native form submissions as far as SleekView Kanban is concerned, and they sit in the right column based on their status field.
Yes. The same capabilities that gate the default WS Form submission screen also gate the SleekView board. A user who cannot see submissions in the standard WS Form admin cannot see them on the board, and read-only roles get a board they can view but not drag on, so the WS Form security model carries through cleanly without extra setup.
Trashed submissions are filtered out of every board by default because the trash status is excluded from the underlying query. You can build a dedicated Trash review board that flips that filter to surface only trashed submissions for restore or permanent delete decisions without polluting the active triage view with deleted records.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout