Yes. SleekView reads sc_orders and sc_tickets directly through the same code path the Event Ticketing report uses, so the add-on does not need any extra configuration beyond pointing SleekView at the table and choosing the order status field as the grouping column.

Yes. Dropping a card into Checked in writes the check-in flag on every sc_tickets row tied to the order, including the timestamp on each row. The default check-in screen reads the same flag, so the board and the screen show identical numbers without a separate sync at any point.

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

Yes. SleekView reads any custom attendee field you configured on the Sugar Calendar Event Ticketing form and lets you choose it for the card front. The value matches what shows in the per-ticket screen because SleekView reads the same row, not a copy stored somewhere else.

Yes. SleekView renders one card per sc_orders row and shows the ticket count on the front, so a buyer who purchased four tickets to the same event shows as one card with a count of four. Expanding the card reveals the linked sc_tickets rows and lets you check in each attendee individually.

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

Yes. The board can show orders across every active event in the calendar, or be filtered to a single event ID for tonight's run. The grouping field stays the order status, only the filter changes per saved view, so a series organiser gets a single live board for the whole run of events.

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