6 shots · about 1 min 05 s of finished video · lesson 6 of Attendance: daily register, alerts, devices and check-in
Record as
Owner (demo_owner)
Sign in at /demo on a demo-mode build
Screens
/attendance/devices /attendance/devices/[id]
Length
1 min 05 s
narration at ~150 words/min + screen time
Status
Not yet recorded
Before recording
Register a device, choose its vendor and serial number, set its punch window and what it marks, and save the one-time API token.
| # | Screen | Action (on screen) | Must be visible | Voice-over | ~s |
|---|---|---|---|---|---|
| 1 | /attendance/devices | Open Attendance → Devices. | Tabs Devices, Unmatched, Import, Rules, Geofences; tiles Active devices, Punches today, Unmatched user ids; a table with Device, Type, Serial, Last seen, Today, Unmatched, Mapped and Open; and an Add device button. The demo school has "Main gate biometric" (eSSL) and "Hostel RFID reader" (ZKTeco). | A device is anything that produces punches: a fingerprint terminal at the gate, a card reader at the hostel, or a virtual device you import CSV logs into. | 15 |
| 2 | /attendance/devices | Click Add device. | The Add device dialog with Name, Type (Fingerprint / biometric, RFID / smart card, Face recognition, QR scanner, GPS geofence (app)), Vendor (eSSL, ZKTeco, Mantra, Realtime, Matrix, Generic / other), Serial number (SN), Location, Timezone, Duplicate window (minutes), Accept punches from / until, Allowed source IPs (optional) and the checkboxes Marks students and Marks staff. | Click Add device to register a new terminal. | 7 |
| 3 | /attendance/devices | Fill Name (for example Main gate biometric), pick Type and Vendor, and type the Serial number (SN) exactly as printed; it is required for ZKTeco/eSSL push. Set Accept punches from 06:30 and until 18:00 so night-time test punches are stored as outside window. Keep Timezone Asia/Kolkata. Callout: Untick Marks students on a staff-room device, or Marks staff on a classroom reader, so a stray punch cannot mark the wrong register. | The hint under the serial field reads "Required for ZKTeco/eSSL ADMS push; printed on the device and under Menu → System info." | Name the device, choose its type and vendor, and type the serial number exactly as printed. | 10 |
| 4 | /attendance/devices | Under Allowed source IPs (optional) enter the school's public IP address (comma-separated if several). Click Add device. | The toast "Device added" and the dialog now shows the alert "Device API token — shown once" with the token in a box and a copy button. | ADMS identifies a terminal only by its serial number, so limiting pushes to the school's IP is the recommended protection. The token is for devices or middleware that push JSON. | 16 |
| 5 | /attendance/devices | Copy the token with the copy button (toast "Token copied"), store it safely, then click Done. Callout: Lost the token? Open the device and click Token to issue a new one; the old one stops working immediately. | The new device appears in the table with Last seen = Never. | Copy the token now: it is shown only once. | 8 |
| 6 | /attendance/devices/[id] | Open the device row. Use Edit to change settings, Deactivate to stop accepting punches (confirm "Deactivate <name>? It will stop accepting punches."), Reactivate to resume, or Delete to remove the device with its events and mappings. | An inactive device shows the alert "Device inactive: Punches from this device are rejected until it is reactivated." | From the device page you can edit, pause, resume or delete the device. | 9 |
After the video is published
Add its YouTube id under attendance-device-add in src/lib/help/videos.ts, with a chapters map of step number → seconds. The lesson page then shows the video and a “Watch this step” link on every step. See the video production guide.