SleekView Kanban for Gravity Flow
Gravity Flow tags each entry with a current step and a workflow_final_status; SleekView groups by that field and lets approvers drag cards from Pending into In Progress, Complete, or Rejected with the step transition firing as usual.
♾️ Lifetime License available
Gravity Flow runs the workflow, kanban shows the queue
Gravity Flow extends Gravity Forms with a real workflow engine: approvals, user inputs, conditional routing, all stored on the existing gf_entry table with extra meta keys in gf_entry_meta. The key fields are workflow_step, workflow_step_status, and workflow_final_status. The default inbox lists entries assigned to the current user, with status changes happening one entry at a time through the step UI.
SleekView Kanban makes that workflow a board. Group by workflow_final_status for a top-level view (Pending, In Progress, Complete, Rejected, Cancelled) or by workflow_step to see the queue per step. Cards show the assignee from the step's user IDs meta, the current step name from the form's workflow config, the SLA timestamp if the step has a due date, and the original submitter for context.
Dragging a card calls Gravity Flow's process_user_input() or process_user_assignee() via the API, so step transitions, notifications, and conditional logic all fire as if an approver clicked Approve in the inbox. Bulk drag is supported for reassignment when a manager rebalances workload across reviewers.
Workflow
How SleekView Kanban reads Gravity Flow data
Connect to Gravity Forms tables
gf_entry as the source and join gf_entry_meta for Gravity Flow keys. SleekView reads the workflow config from the form to expose human-readable step names.
Group by workflow status
workflow_final_status for an overall board or workflow_step for a per-step view. The board renders one column per value with row counts so backlog is obvious.
Pin assignee and SLA to cards
Enable drag-to-advance
Sample board
Sample Gravity Flow workflow board
Comparison
Default Gravity Flow inbox vs SleekView Kanban
Default Gravity Flow Inbox
- Inbox shows entries assigned to the current user, not the whole queue
- Status views are filter tabs, not columns visible together
- Assignee load across reviewers is invisible without status reports
- SLA timestamps live on the step page, not on a queue overview
- Bulk reassignment requires per-entry edits through the admin screen
SleekView Kanban
-
Groups by
workflow_final_statusorworkflow_step - Cards show assignee, step name, SLA, and original submitter
- Drag calls Gravity Flow step processing, so hooks and notifications fire
- Colour rules surface overdue SLAs on the card front
- Filters scope to one form, one assignee, or one step
Features
What SleekView Kanban gives you for Gravity Flow
Drag is a real step transition
Moving a card from Pending into In Progress or from In Progress into Complete calls Gravity Flow's processing methods, so approvals, rejections, and conditional routing fire the same hooks the inbox triggers.
SLA visibility built in
When a step has a due date, the SLA timestamp lands on the card front with a colour rule for overdue items. Managers see slipping work without opening each entry.
Assignee load at a glance
Group by assignee instead of status for a workload board, or filter the main board to a single user to see what one reviewer needs to handle next.
Audience
Who runs Gravity Flow boards with SleekView Kanban
HR ops
Time off, expense, and onboarding workflows all land on one board scoped by form, with the current step on every card so HR sees who is blocked on what.
Compliance and finance
Vendor and contract approvals flow through a multi-step board with SLA timestamps on every card, and a colour rule highlights overdue compliance checks.
IT and procurement
Hardware requests and access provisioning move through assignment, approval, and delivery columns, with the requester and assignee on every card for handoffs.
The bigger picture
Why Gravity Flow needs a queue view
Gravity Flow is a serious workflow engine that turns Gravity Forms into a routing and approval system. The trade-off is that the default Inbox is built for the individual reviewer: it shows what is assigned to you right now. A team lead, a compliance officer, or a finance manager needs a view of the queue itself: how many requests are pending, which steps are blocked, who is overloaded, which SLAs are slipping.
SleekView Kanban reads the same Gravity Forms tables, surfaces the workflow meta Gravity Flow already maintains, and groups entries by the field that matters for the view: final status, current step, or assignee. Drag-to-advance routes through Gravity Flow's own processing methods, so step transitions, notifications, and conditional routing fire as if a user clicked Approve in the inbox. The plugin keeps owning the workflow logic.
The board owns the queue.
Questions
Common questions about SleekView Kanban for Gravity Flow
Either workflow_final_status for an overall board (Pending, In Progress, Complete, Rejected, Cancelled) or workflow_step for a per-step view. Both are standard meta keys Gravity Flow writes to gf_entry_meta, so no extra integration is needed.
Yes when configured. SleekView calls Gravity Flow's step processing methods, which means a drag from Pending to Complete on a User Input step triggers the approval path, fires step transition hooks, and routes the entry to the next step exactly as the inbox does.
Gravity Flow stores assignee user IDs in step meta. SleekView reads those IDs and shows display names on the card front. Group by assignee or filter by a single user to build a personal workload view from the same board.
Yes. When a Gravity Flow step has a due date, the SLA timestamp is exposed on the card. Colour rules can highlight cards approaching the deadline in amber and overdue cards in red so managers spot slipping work without opening entries.
Drag is configurable per step type. For approval and user input steps, dragging into the target column calls the processing method with the chosen outcome. For automation steps (notifications, feeds), the board is read-only because the step runs without user input.
Yes. The form_id column on gf_entry is filterable, and saved views support one form, several forms, or all forms. Each view is gated by WordPress capability so HR and finance can each have their own board.
Yes. SleekView paginates per column and queries indexed columns on gf_entry for the group-by. Workflow meta is lazy-loaded from gf_entry_meta only for visible cards, so a workflow with thousands of completed entries still renders the active columns quickly.
No. The inbox stays where it is for personal review. SleekView Kanban adds a queue-level board so managers, compliance officers, and team leads see workload, SLA, and step state at a glance without each opening their own inbox.
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