SleekView Kanban for Advanced Custom Fields
SleekView Kanban reads any ACF select, radio, or true_false field on a post type and renders one card per post, grouped into columns by the status value you pick. Dragging a card writes the new value back to post meta in a single AJAX call.
♾️ Lifetime License available
Why ACF posts need a kanban view
Advanced Custom Fields stores its values in the wp_postmeta table keyed by post ID. The default WordPress edit screen lists posts in a vertical table, sorted by date, with no native way to group records by an ACF select value like project_stage or review_status. Teams that track work in custom post types end up scrolling rows and clicking into each post just to read where it sits in a pipeline.
SleekView Kanban connects directly to your ACF field group definition. It reads the choices from any select, radio button, or true_false field and turns each one into a column. Cards pull the post title, featured image, and up to six other ACF fields, so you see the meaningful context for each record without opening the editor. The plugin works on default ACF storage and on serialized repeater rows where the status is a top level field.
Dragging a card calls update_field() on the new column value and fires acf/save_post, so any ACF action you have wired up continues to run. Conditional logic, validation rules, and audit log integrations stay intact. If the field has no value, the card lands in a dedicated unassigned column you can hide or rename.
Workflow
From ACF field group to live board in four steps
Connect to your ACF field group
Pick the status column to group by
Choose what shows on each card
Enable drag and drop writes
Sample board
Sample ACF project tracker board
Comparison
Default ACF admin versus SleekView Kanban
Default ACF post list
- Posts render as a flat WP_List_Table sorted by date with no status grouping option
- Reading an ACF value forces a click into the post editor, one record at a time
- Bulk edit only exposes core post fields, never ACF select or radio choices
- No drag and drop, no visual signal of where work is stuck in the pipeline
- Switching the status of ten posts means ten editor loads and ten saves
SleekView Kanban
-
Reads ACF choices directly from
get_field_object(), no manual column setup - Cards render text, image, user, and date fields with native ACF widgets
-
Drag fires
acf/save_postso audit logs and webhooks still trigger - Respects ACF Pro location rules, taxonomy filters, and capability checks
-
Falls back to read only mode for users without
edit_postson the post type
Features
What SleekView Kanban gives you for Advanced Custom Fields
Any ACF field can be the status
Select, radio, and true_false fields all work as the grouping axis. The board reads field choices in their registered order, so columns line up with whatever taxonomy of stages you already use. Renaming a choice in ACF renames the column on next reload.
Drag writes through update_field
Every card move calls update_field on the post and fires acf/save_post. Validation, conditional logic, and any acf/update_value filters you have registered keep firing. Audit log plugins capture the change like any other admin edit.
Filter by any ACF field
Add a filter bar that targets text, number, taxonomy, or user fields. Filters apply on the server through meta_query, so boards stay fast on tens of thousands of posts. Saved views remember filter state per user.
Audience
Three ACF post types that need a board
Project trackers
A Projects post type with a project_stage select field becomes a sprint board. Assign owners through a user field, due dates through a date field, and drag projects across columns as work progresses.
Editorial pipelines
Article post types with a workflow_status field render as a newsroom board. Editors see drafts, review, scheduled, and published columns and move pieces forward by dragging cards instead of opening posts.
Sales opportunities
Opportunity post types with deal_stage and deal_value fields become a pipeline view. Cards show the dollar amount and account owner, and dragging to closed won fires the same hooks as a manual save.
The bigger picture
Why kanban beats the ACF edit screen
Advanced Custom Fields is the most popular metadata layer in the WordPress ecosystem, and it earned that spot because the form builder is unmatched. The reporting layer has not kept up. The plugin still leaves you in the default post list when you want to see how a hundred records are distributed across a status field, and that view forces a sequential read.
You scroll, you click, you load an editor, you scroll back. For any post type that represents stateful work, that pattern wastes hours every week. A kanban board solves the reporting half of the problem without giving up the form half.
The status field stays in ACF where you defined it, with the same choices and the same validation. The board is a second window onto the same data, optimized for triage instead of authoring. Teams that switch tend to discover that the bottleneck was never the editor.
It was the inability to see the queue.
Questions
Common questions about SleekView Kanban for Advanced Custom Fields
Both. SleekView Kanban only needs the core ACF API, so the free version is enough for basic boards. ACF Pro unlocks repeaters, flexible content, and clone fields, which the board can display on cards but cannot use as the grouping axis since they hold multiple values.
Select, radio button, button group, and true_false fields. These all expose a single value with a predictable set of choices, which maps cleanly to kanban columns. Multi select, checkbox, and taxonomy fields are not eligible as the grouping axis but can still appear on cards.
They fire exactly as they would on a manual save in the post editor. The plugin calls update_field on the new value and then triggers the full ACF save lifecycle. Audit logs, integrations, and any custom acf/update_value filters stay in the loop with no extra wiring.
Card layouts can display top level fields and a single repeater row chosen by index. Grouping by a value inside a repeater is not supported because a single post can hold many rows with different statuses, which would force the same card to live in multiple columns.
Unassigned posts land in a dedicated Unassigned column at the far left. You can rename it, hide it, or treat it as a fifth swim lane. Dragging a card out of Unassigned writes the chosen column value to the status field on the next save.
Yes. The board only loads field groups that ACF says apply to the post, and the underlying WP_Query respects current_user_can on every record. Users who lack edit_posts on the post type see a read only board with a tooltip on the drag handle.
Vertical order inside a column is stored in a dedicated meta key on each post called _sleekview_kanban_order. You can sort cards by that key, by a date field, or by a number field. Reorder changes do not trigger acf/save_post since no ACF field value changed.
Boards stream cards lazily per column, so the row count limit is whatever your database can scan. In practice boards stay responsive into the hundreds of thousands of posts as long as the status field has an index on the meta_value column.
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