Yes. SleekView reads em_booking posts directly through the same code path the EventPrime report screen uses, so the front-end form does not need any extra configuration beyond pointing SleekView at the custom post type and choosing the status meta as the grouping column.

Yes. Dropping a card into Confirmed writes the new value to _em_booking_status and fires the EventPrime booking status action, so the confirmation email configured in the plugin settings goes out exactly as it would from the report screen. The audit log records the drag too.

Yes. Dropping a card into Attended writes the new value to the status meta and stamps the attendance flag the EventPrime report reads. The default attendance column on the report shows the same value, so the board and the report show identical numbers without a separate sync.

Yes when the linked Stripe or PayPal payment ID exists on the booking meta. Dropping a card into Refunded triggers the refund flow on the payment record through the same hook the report screen uses, so receipts and emails behave exactly as if the refund was issued from the row.

Yes. SleekView reads any custom booking field you configured on the EventPrime booking form and lets you choose it for the card front. The value matches what shows in the booking record because SleekView reads the same meta the record reads, not a copy stored separately.

Yes. Saved kanban views are scoped per role and per capability, so door staff can see Confirmed and Attended only, finance can see Refunded, and the organiser sees all four columns. The underlying em_booking data does not change, only what each role reads on the board.

Yes. The board can show bookings across every active event in the calendar, or be filtered to a single event ID for tonight's run. The grouping field stays the status meta, 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 calendar with several thousand bookings renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before the board renders.