SleekView Kanban for Event Organiser
Event Organiser stores events as event posts with WordPress post statuses and, with the Pro Bookings add-on, stores bookings with confirmed, pending, or cancelled states. SleekView Kanban renders one card per row and groups them into columns you drag cards between.
♾️ Lifetime License available
Read Event Organiser posts and bookings as a board
Event Organiser stores every event as a custom event post with standard WordPress post_status values like draft, pending, publish, private, and trash, plus the plugin's own occurrence and venue tables. With the Pro Bookings add-on, every ticket lands in eo_bookings with a status like confirmed, pending, cancelled, or payment_pending.
SleekView Kanban reads the same posts and bookings table and groups them into columns by status. For the editorial board the natural grouping is post_status, so the board shows Draft, Pending review, Published, and Cancelled. For the bookings board the grouping is the booking status column with Pending, Confirmed, Cancelled, and Payment pending as stacks. Each card carries the title, the start datetime, the venue, and the ticket count or attendee name.
Dragging a card writes the new state back to the source row. Moving an event into Published makes it visible on the public calendar instantly, and moving a booking from Pending to Confirmed runs through Event Organiser's own booking update path so confirmation emails, calendar syncs, and any payment hooks fire as expected.
Workflow
From event and booking rows to a draggable board
Connect SleekView to Event Organiser
event posts and, if installed, for the Pro Bookings table. SleekView reads the occurrence, venue, and category meta automatically and joins to ticket type definitions.
Pick the status column to group by
post_status for editorial boards or the bookings status column for ticket boards. SleekView lists every distinct value present and renders one kanban column per state, including any custom statuses.
Choose what shows on each card
Enable drag to update status
post_status and dragging a booking card calls Event Organiser's booking update path. Editor notifications, calendar updates, and payment hooks fire as expected.
Sample board
Sample Event Organiser bookings board
Comparison
Default Event Organiser admin vs SleekView Kanban
Default Event Organiser admin
- Events admin is a long table sorted by event date with status as a small label per row
- Bookings screen lives in a different report and shows status only as a column
- No glance count of how many drafts, pending bookings, or cancellations sit at each stage
- Editorial review and ticket reconciliation happen on different screens with different filters
- Bulk status changes are limited to the WordPress bulk-edit dropdown for events
SleekView Kanban
-
Groups
eventposts and Pro Bookings into one board per scope with live counts -
Drag an event card to flip
post_statusthrough standard transition hooks -
Drag a booking card to update
eo_bookingsthrough the plugin's own update path - Cards show title, start, venue, attendee, ticket type, and total in one readable tile
- Per-event saved views give each producer a focused board for their own shows
Features
What SleekView Kanban gives you for Event Organiser
Group by any status field
Use post_status on events or the booking status on Pro Bookings. SleekView lists every distinct value in the column and renders one board column per status, with counts that update live as you drag cards across stages.
Drag to update events or bookings
Drag an event from Draft to Published or a booking from Pending to Confirmed. SleekView calls the same update paths the admin uses, so transition hooks, confirmation emails, and payment integrations behave consistently.
Configurable card fields
Pick which fields land on each card: event title, start datetime, venue, attendee, ticket type, total, or any custom meta. Dates and currency format themselves and venue IDs resolve into readable labels.
Audience
Who runs Event Organiser on a kanban board
Editorial teams
Writers drop new event drafts into Pending review, editors drag the approved ones into Published, and producers handle Cancelled when a venue or schedule falls through, all on one screen.
Booking coordinators
Open the bookings board, drag Payment pending entries into Confirmed once the transfer lands, and drag Cancelled refunds through to closure with a note for the audit log.
Promotions teams
Filter to Published events for the next 14 days to plan the newsletter, then switch to the bookings board to see ticket sales velocity per event for the same window.
The bigger picture
Event Organiser data is two pipelines, one board
Event Organiser runs two related pipelines at once: events get edited, reviewed, and published, while tickets get pending, confirmed, paid, and sometimes refunded. The default WordPress admin lists each pipeline in its own table sorted by date, which works for a quiet calendar and falls apart for a venue running multiple shows a week. The board view fixes this by making the only state that matters, the status, the primary axis of the screen.
The editorial board shows Draft, Pending review, Published, and Cancelled with a count at the top of each column. The bookings board shows Pending, Confirmed, Payment pending, and Cancelled with attendee and ticket details on every card. Drag is the natural verb for moving an event into Published or a booking into Confirmed, and because SleekView writes through Event Organiser's own update paths, every drag still triggers the editorial hooks, the booking confirmation emails, and the payment captures you already configured.
The events admin and the bookings report stay available for the back office while the board gives the producer and the ticket coordinator a single screen for the work.
Questions
Common questions about SleekView Kanban for Event Organiser
Both. The editorial board reads event posts and works on the free plugin. The bookings board requires the Pro Bookings add-on because that is what creates the eo_bookings table SleekView reads for ticket status. You can run either board independently or both side by side.
Yes. Dropping a card into the Published column writes publish to post_status on the underlying event post, which fires the same transition_post_status hooks the default admin does. The public Event Organiser calendar reads the new value and the event appears without a manual refresh.
Yes. Dropping a booking card into Confirmed or Cancelled writes the new status to eo_bookings through Event Organiser's own booking update path. Confirmation emails, calendar syncs, and any payment hooks you have configured fire exactly as if you had used the standard admin.
Yes. SleekView reads the distinct values present in the grouping column and renders one kanban column per value. If you have registered a custom post status like Cancelled or Postponed through a snippet or extension, those appear next to the built-in WordPress statuses without extra setup.
Yes. Saved kanban views are scoped per role and per capability, so writers can see Draft and Pending review only, editors can see all columns, and contributors can drag only their own posts. The WordPress capability checks on edit_post still apply on every drag.
Yes. SleekView reads the occurrence meta the plugin writes, so a recurring series appears as a single card by default with the next occurrence on the front, or you can expand it to one card per occurrence if your workflow tracks them separately. Status changes apply to the series unless you target a single occurrence.
Yes. SleekView reads state on a short interval and reconciles drags against the live record, so if a colleague has already confirmed a booking on their screen, you see the new state before your drag conflicts. Optimistic updates revert cleanly on rejected writes.
Yes. SleekView only loads cards for the columns currently visible and paginates older rows into a scroll-on-demand tail. Indexing on post_status and on the booking status column keeps group counts cheap even for venues with years of archive data.
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