Check-in points (event page)

The panel on an event that lists where people are scanned: group pre-checks, venue gates, zones inside, kiosks.

Who opens it: an organizer with checkin.manage_points (Owner, Admin), setting an event up or re-pinning the day before. Everyone else with events.read sees the list read-only.

What they came to do: say where scanning happens, when each point is open, and what it lets through.

What must be true when they leave: every point that can scan is one the plan allows, its hours mean the local clock at that place, and its policy is one the scanner can honour.

Decided

• Opening hours are local wall time per day (03:30), and every row shows what it resolves to in the event's timezone and in UTC — "Sat Nov 7, 03:30–12:00 CST = 09:30–18:00 UTC" (L17). Hours that close before they open run past midnight. No hours for a day: open whenever scanned.
• Only points that can scan count. check_in_points_max limits switched-on points per event; zones need zones and pre-checks need satellite_checkin to be switched on. A switched-off point can always be created, kept and switched off — that is how an event template on a smaller plan arrives (EVENT_TEMPLATE_FORMAT §1.5). At the limit, "Add" is still offered and "More check-in points" opens the upgrade.
• A point with check-ins is never deleted — switch it off (check-ins are append-only).
• Policy defaults per kind are shown as their effective values: gates and kiosks day-lock, pre-checks search by name, typed codes are off everywhere, zones need a gate scan first, kiosks have no overrides.
• Kiosk is offered as a kind with the kiosk_mode flag (beta, week 20); a point already a kiosk keeps it. A kiosk has no override roles, no "Search by name" and no "Typed codes" — saving one with them is refused — because it finds people with its own search (kiosk.md).
• Visibility: a point attached to a group (a group's pre-check) is seen inside that group's subtree; a point for the whole event (a gate) is seen by everyone.

Open

• Devices are managed in their own panel (devices.md); this list does not yet show which devices point at a point.
• Venue per point is not offered; gates take the event's venue.