Yes. SleekView reads ai1ec_event_ticket and ai1ec_transaction directly through the same code path the bookings screen uses, so the Tickets add-on does not need any extra configuration beyond pointing SleekView at the table and choosing payment_status as the grouping column.

Yes. Dropping a card into Checked in writes the check-in flag the AI1EC bookings screen uses, including the timestamp. The default check-in column in the bookings list reads the same flag, so the board and the list show identical numbers without a separate sync step at any point.

Yes. Dropping a card into Refunded triggers the refund flow on the linked ai1ec_transaction through the same hook the transaction screen uses, so receipts and emails behave exactly as if the refund was issued from the row. SleekView records the drag in the audit log.

Yes. SleekView reads any custom booking field you configured on the AI1EC ticket form and lets you choose it for the card front. The value matches what shows in the bookings screen because SleekView reads the same row, not a copy stored somewhere else.

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 ai1ec_event_ticket data does not change, only what each role reads on the board.

Yes. Free events still write rows to ai1ec_event_ticket with payment_status set to a paid-equivalent value. SleekView reads the same field and groups the rows the same way, so RSVP-only events show a board with Pending, Going, and Checked in columns based on the values in your data.

Yes. SleekView reads the distinct values present in payment_status and renders one kanban column per value. If you registered a custom payment status through a snippet or a third party gateway, 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 a conference series 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 render.