Yes. SleekView reads sec_registration posts and the related meta keys directly through the same code path the registrations report 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.

Yes. Dropping a card into Approved writes the new value to _sec_registration_status and fires the registration status hook, so the approval email configured in the Stachethemes calendar settings goes out exactly as it would from the registrations report. The audit log records the drag too.

Yes. Moving a card into the Checked in column writes the check-in flag the Stachethemes registration record uses, including the timestamp. The default check-in toggle on the registration screen reads the same flag, so the board and the screen show identical numbers without a separate sync.

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

Yes when the paid tickets add-on is active. Dropping a card into Cancelled flips the status and triggers the refund flow on the linked payment row through the same hook the registration screen uses, so receipts and emails behave exactly as if the cancel was issued from the record.

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

Yes. The board can show registrations 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 one live board for the whole run of events.

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.