SleekView Kanban for FormCraft
SleekView reads the FormCraft submissions table, groups every entry into status columns like New, Read, Spam, and Trash, and lets your team drag a card from one column to the next while the underlying row is updated in the same transaction.
♾️ Lifetime License available
Why FormCraft entries belong on a board
FormCraft stores every submission in its own database table with a status column, an author, a timestamp, and a JSON blob of field values. The default admin screen renders this as a single paginated list which works for one form and one reviewer but breaks down the moment two people are triaging entries from a contact form, a quote request form, and a job application form at once.
SleekView reads the FormCraft submissions table directly and treats the status field as the natural grouping axis. Every row becomes a card; every distinct status value becomes a column. You pick which fields show on the card front, usually the submitter name, the form title, and the submission date, and SleekView renders the whole pipeline as a kanban that any logged-in user with the right capability can see and edit.
Dragging a card from New to Read writes the new status back to the FormCraft row, fires the same hooks as the admin screen, and respects the role permissions you already configured. Spam moves go to the spam column without deleting the record, trash sends them to the trash status, and an undo toast gives a five-second window to put a card back if someone moved the wrong one.
Workflow
From FormCraft table to live kanban in four steps
Connect FormCraft
Pick the status column
Choose what shows on each card
Enable drag and drop
Sample board
Sample FormCraft submissions board
Comparison
FormCraft default vs SleekView Kanban
Default FormCraft entries
- Single paginated list of submissions with no per-status grouping or board view
- Status changes require opening each entry individually, no bulk drag and drop
- No way to pin priority fields like name or company to a card-style front
- Filtering by form and status uses separate dropdowns that reset on reload
- Multiple reviewers see the same flat list with no signal who is working what
SleekView Kanban
- Reads the FormCraft submissions table live, no extra sync job to maintain
-
Groups by the real
statuscolumn, including custom values from filters - Drag-drop writes update the row and fire the standard FormCraft hooks
- Card front fields are configurable per board, not hardcoded to name and date
- Undo toast catches stray drops within a five-second window before commit
Features
What SleekView Kanban gives you for FormCraft
Drag-to-update writeback
Move a card from New to Read and SleekView updates the FormCraft row in the same transaction. The standard submission hooks fire, so any notification or integration tied to a status change still runs without extra plumbing.
Per-form board filters
Filter a board to one form, a date range, or a custom field value. The status columns stay intact and only the cards inside them update, so a team focused on quote requests can ignore the contact form entries entirely.
Role-aware writes
SleekView respects the FormCraft capability that controls who can edit submissions. Reviewers without write rights still see the board but cannot drag cards, which keeps audit history clean and predictable for compliance reviews.
Audience
Three teams that use a FormCraft kanban every day
Recruiting triage
Each job application becomes a card. Recruiters drag candidates from New to Shortlisted to Interview without leaving WordPress, and the FormCraft data behind every card stays the source of truth.
Sales quote pipeline
Quote requests land in New, account reps move them to Qualified or Sent. The card front shows budget and company so the team can prioritise the high-value leads before the small ones.
Support inbox cleanup
Contact form messages get triaged into Read, Replied, and Spam. Junk drops out of the active columns without losing the record, which keeps the legitimate threads easy to scan at a glance.
The bigger picture
Why a board view changes how teams handle submissions
Form submissions are a stateful workflow, not a static log, and FormCraft already knows that — every entry has a status field. The problem is that the default admin screen renders them as a single flat list, so the state is invisible until you open each row. A kanban view fixes that mismatch.
Every reviewer can see, at a glance, how many entries are waiting, how many are in progress, and how much spam slipped through, and they can move work along by dragging a card instead of opening, scrolling, and clicking save. The writeback path matters because it means the board and the database stay in sync without a separate sync job, and the role-aware writes mean the same board can be shown to reviewers and read-only stakeholders without risk. The result is a workflow that looks like the rest of the team's tools, lives inside WordPress, and runs against the data FormCraft already stores.
Questions
Common questions about SleekView Kanban for FormCraft
No. SleekView reads from the existing FormCraft submissions table and writes status updates back into the same column FormCraft already manages. There is no shadow table, no schema migration, and uninstalling SleekView leaves every submission exactly where FormCraft stored it.
SleekView reads the distinct values from the status column at board load, so any custom status value automatically becomes its own column. You can rename, recolour, or hide that column from the SleekView settings without touching FormCraft itself.
Yes. Each drag is a small write keyed by the submission ID, so two reviewers updating different cards never collide. If both reviewers happen to drag the same card within a second, the second write wins and a toast warns the first reviewer that the card moved on them.
Yes. SleekView calls the same capability check FormCraft uses for its own admin screens. Reviewers without the edit capability still see the board and can read every card, but the drag handles are disabled and the writeback API rejects the request server side.
No. Moving a card to the Trash column writes the trash status to the row, which is the same soft-delete state the FormCraft admin screen uses. The record stays in the database and can be restored by dragging it back to any other column.
The board polls for new entries on a configurable interval and adds them to the appropriate status column without a full page reload. You can also trigger a refresh manually from the board toolbar if you want an instant update after a known submission.
Yes. Each board has a filter that narrows the source rows by form ID, date range, or any field value. The status columns and card layout stay the same, only the cards that match the filter render, which lets one team focus on one form without distractions.
Submitter name and form title carry most of the signal, with submitted date as the third anchor. Adding a short excerpt of the message field helps reviewers decide which entries to open. Badge-style fields like priority or source can sit on top of the card for one-glance triage.
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