Yes. SleekView reads evo_rsvp for RSVPs and evo_tx for ticket buyers on the same board. Cards show the ticket type so you can tell an RSVP card from a paid ticket card at a glance and group both by the combined status field.

Yes. Dropping a card into the Checked in column writes the check-in meta the EventON Tickets add-on uses, including the timestamp. The default ticket report reads the same key, so the board and the report show identical numbers without a separate sync step at the end of the day.

Yes. Dropping a ticket card into Refunded triggers the refund flow on the linked payment record through the same hook EventON uses inside the ticket report, so receipts and emails behave exactly as if the refund was issued from the row. The drag is logged in the audit log.

Yes. SleekView reads any custom RSVP field you configured on the EventON form builder and lets you choose it for the card front. The value matches exactly what shows in the RSVP report because SleekView reads the same meta the report does, not a parallel copy.

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

Both. You can scope a saved board to a single event by event ID for tonight's run, or run an aggregate board across every upcoming event for a series organiser. The grouping field stays the same, only the filter changes per saved view.

Yes. SleekView reads the distinct values present in the grouping column and renders one kanban column per value. If you registered a custom status through an EventON snippet or a third party add-on, that value shows as a column next to the built-in ones with no extra configuration.

No. SleekView paginates inside each column and loads card detail on demand, so an event series with several thousand RSVPs and tickets renders the column counts immediately and streams card content as you scroll. Filters reduce the working set before the board renders.