✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Event Espresso 4 Pro

Event Espresso 4 Pro stores registrations as rows in esp_registration with codes like RPP, RAP, RCN, and RNA. SleekView Kanban reads those rows and renders one card per registration, grouped into columns you can drag cards between to update the status.

♾️ Lifetime License available

SleekView Kanban board for Event Espresso 4 Pro

Read Event Espresso registrations as a board

Event Espresso 4 Pro tracks every registration as a row in esp_registration with STS_ID as the status code. The built-in codes are RPP for Pending Payment, RAP for Approved, RNA for Not Approved, RCN for Cancelled, RDC for Declined, and RWL for Wait List, with the matching label held in esp_status. Payment data lives in esp_payment and check-in writes esp_checkin against the registration row.

SleekView Kanban reads the same registration rows and groups them into columns by STS_ID. The board shows Pending, Approved, Checked in, and Cancelled as separate stacks. Each card carries the attendee name, the event title, the ticket type, and the registration total from esp_transaction, so organisers see what they need without opening the registration row.

Dragging a card writes the new value back to STS_ID and fires the same hook the registration screen fires. Moving a card from Pending into Approved sends the approval email registered through Messages, moving into Checked in writes an esp_checkin row with the timestamp, and moving into Cancelled flips the status the registration list reads. The audit log records every drag for staff accountability.

Workflow

From esp_registration rows to a board

1

Connect SleekView to Event Espresso

Add a SleekView data source for esp_registration with joins to esp_transaction, esp_payment, esp_attendee, and esp_event. SleekView auto-detects the Messages add-on for status change hooks.
2

Pick STS_ID as grouping column

Switch the view to Kanban and choose STS_ID as the grouping column. SleekView renders one column per status code with the human label from esp_status, and you can rename or reorder the columns.
3

Choose what shows on each card

Set the card front to attendee name, event title, ticket type, and registration total. Add any registration question answer you configured through Event Espresso question groups for the card front.
4

Enable drag to update status

Turn on drag-and-drop and SleekView writes the new STS_ID back to the registration row and fires the registration status change action. The Messages add-on sends the right email and the audit log records the move.

Sample board

Sample Event Espresso registrations board

Four columns built from live esp_registration rows on a Pro install, with the cards the organiser drags as registrations are approved, paid, and checked in at the door on event day.
Pending Payment
47
Anna Kovac, Summer Conference 2026
RPP, 249.00 USD due today
Liam Park, Advanced Track Workshop
RPP, 89.00 USD due Friday
Priya Anand, Half-day Tutorial
RPP, 59.00 USD invoice sent
Approved
168
Marcus Webb, Summer Conference 2026
RAP, 249.00 USD paid
Helena Voss, Advanced Track Workshop
RAP, 89.00 USD paid Wednesday
Tomasz Kowal, Half-day Tutorial
RAP, 59.00 USD paid Thursday
Checked in
112
Daniel Ortiz, Summer Conference 2026
Scanned 09:42, Day pass holder
Sara Ono, Advanced Track Workshop
Scanned 13:05, Workshop pass
Karim Idris, Half-day Tutorial
Scanned 14:30, Tutorial pass
Cancelled
23
Eli Berger, Summer Conference 2026
RCN, Cancel reason recorded
Mia Tanaka, Advanced Track Workshop
RCN, Refund issued today
Adrian Cole, Half-day Tutorial
RCN, Wait list moved up

Comparison

Default registration list vs SleekView Kanban

Default Event Espresso list

  • Registration list is a paginated table sorted by date with STS_ID hidden behind a label
  • No way to drag registrations from pending payment to approved to checked in on a board
  • Payment, check-in, and cancellation are spread across separate report screens with filters
  • Question group answers are buried behind a per-registration modal, not on the card front
  • Bulk status changes go through a select dropdown rather than a draggable column move

SleekView Kanban

  • Groups esp_registration rows on one board by STS_ID
  • Drag a card to flip STS_ID and fire the same hook the registration screen fires
  • Card front shows attendee name, event title, ticket type, and registration total
  • Reads question group answers from esp_answer onto the card front
  • Audit log records every drag with user, timestamp, and previous STS_ID code

Features

What SleekView Kanban gives you for Event Espresso 4 Pro

Real registration cards

One card per row in esp_registration with the attendee name, event title, ticket type, and registration total from esp_transaction, plus any question group answer you configured through Event Espresso forms.

Drag to flip STS_ID

Moving a card writes the new STS_ID to the registration row and fires the status change action, so Messages sends the right email and the registration list, the payment report, and the check-in screen all read the new value.

Per-role saved boards

Scope the board so door staff see Approved and Checked in only, organisers see all status codes, and finance gets a board focused on Pending Payment and Cancelled rows with the totals from the linked esp_transaction record.

Audience

Who runs Event Espresso registrations on a kanban board

Door staff at conferences

Open the board on a tablet, find the attendee, drag the card from Approved to Checked in. SleekView writes an esp_checkin row with the timestamp and the registration list reads it.

Conference organisers

Watch registrations move between Pending Payment and Approved through the run-up so the room count and the catering order match the actual confirmed attendee total.

Finance teams on payments

Filter the board to Pending Payment to chase outstanding invoices against the esp_transaction totals in a single pass without opening each registration row by hand.

The bigger picture

Registrations have stages, list views hide them

Event Espresso has a clear set of registration stages. Pending Payment becomes Approved when the invoice is paid, Approved becomes Checked in at the door, and sometimes a Wait List row gets moved up to Approved when a cancellation comes through. The plugin stores all of that in esp_registration with STS_ID as a three-letter code, but the default reading surface is still a paginated list sorted by registration date with the status hidden behind a small label per row.

Seeing how many registrations are still Pending Payment a week out takes a filter, a sort, and a count in your head. SleekView Kanban turns the same data into a board with Pending Payment, Approved, Checked in, and Cancelled as columns, a count per column at the top, and a card per registration with the fields the organiser actually reads. Drag a card to flip STS_ID and the registration row updates, Messages fires the right email, and the payment and check-in reports read the new value because SleekView writes to esp_registration.

Questions

Common questions about SleekView Kanban for Event Espresso 4 Pro

Yes. SleekView reads STS_ID directly and renders one column per code with the label from esp_status. RPP becomes Pending Payment, RAP becomes Approved, RCN becomes Cancelled, RWL becomes Wait List, and any custom code you registered shows as its own column on the board.

 

Yes. Dropping a card into a new column writes the new STS_ID through the same code path the registration screen uses, so the registration status change action fires and the Messages add-on sends the right email. The audit log records the move with the previous code for staff accountability.

 

Yes. Moving a card into the Checked in column writes an esp_checkin row with the registration ID and the timestamp. The default check-in report reads the same table, so the board and the report show identical numbers without a separate sync or batch step at the end of the event day.

 

Yes. SleekView reads esp_answer for any question group you configured and lets you choose any answer for the card front. The value matches exactly what shows in the registration screen because SleekView reads the same row, not a copied or denormalised version stored somewhere else in the database.

 

Yes. Wait List is one of the built-in STS_ID codes, so SleekView renders a Wait List column next to the others. Dragging a registration into Wait List flips STS_ID to RWL, and dragging back out flips it to RAP or RPP. The wait list emails fire through the registration status change hook as expected.

 

Yes. Saved kanban views are scoped per role and per capability, so door staff can see Approved and Checked in only, finance can see Pending Payment and Cancelled, and the organiser sees every STS_ID code. The underlying registration data does not change, only what each role reads on the board.

 

Yes. The board can show registrations across every active event for a conference series, or be filtered to a single event ID for tonight's run. The grouping field stays STS_ID, only the filter changes per saved view, so a series organiser gets a single live board for the whole run.

 

No. SleekView paginates inside each column and loads card detail on demand, so a conference with several thousand registrations renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before the board even renders.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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