Check-in & Attendance¶

Members get in and out through the kiosk (RFID / PIN), the manual buttons on the Team table, or the Discord !checkout. All of it lands in the same table: team_member_sessions.

The Attendance view (admin)¶

A records-management grid rather than a "who's in the room" board (that live list is the kiosk's checked-in panel).

Columns: Member, Session, Check In, Check Out, Last Update, Status (Checked In / Completed).

Order: most recent activity first. A record's last activity is its check-out if it has one, otherwise its check-in — so a visit closed an hour ago sits above one opened this morning, and the Last Update column is the key the list is sorted on. The ordering happens in SQL, so it holds across pages rather than only within the page on screen.

Filters:

Every filter, the search included, is applied server-side across the whole table — not to the rows currently on screen. Searching a name finds it whether or not it is on the current page, and the pager then reports how many records matched ("N matches", "Page 2 of 7"). When nothing matches, the table says so and offers Clear filters rather than simply going blank.

Row actions:

• Edit Check-In — opens pickers for check-in and check-out times (correct a mis-tap, or fix a scanned time).
• Delete — remove a record.
• Clear All Attendance — wipe the whole table (with confirmation). One request, one transaction: it used to delete a row per request, which on a remote server took minutes.

Manual check-in / check-out¶

The same mutation powers everything, and toggles: if the member is checked in anywhere they are checked out, otherwise checked in.

• Team table rows carry per-member Check In / Check Out buttons.
  • Check In asks where: a dialog lists every location with the session a check-in there would join ("today, 6:00 PM – 9:00 PM"), and greys out the ones with nothing running. The location belongs to the check-in, not to the machine — an admin's laptop has no kiosk location and does not need one.
  • Check Out only confirms, naming the session it will close. No location is involved: the open record already knows which session it belongs to.
  • Both are recorded with a source of admin, so the statistics do not claim a member tagged in at a reader they never touched.
• The kiosk's Kiosk Check In / Out dialog searches members and toggles rows, using that device's configured location (its checkout needs none either).
• The Discord !checkout lets a linked member check themselves out.

These write to team_member_sessions, which the kiosk role and any team_member_sessions: write grant allow.

Check-in windows¶

A tap counts as checking in to a session only when it is within 4 hours of that session's start or end (configurable via Check-in Window). With no qualifying active session the kiosk reports "No active session at this location." Full mechanics on the Check-in Windows & Auto Checkout page.

What happens at the end¶

• A session whose end has passed enters overtime for anyone still checked in (kiosk counts it as OVERTIME in red).
• After the grace period (24 h by default) — or the moment the next session at that location starts — lingering members are auto-checked-out at the session's end time, and a Discord DM is offered.
• Sessions with nobody left checked in are marked Finished.

All of this is recorded with a source of truth (kiosk / RFID / Discord / auto) and shows up in Leaderboard & Statistics as regular vs overtime hours.