Face recognition · QR · IP attendance
Prove presence with face recognition — and QR when you need it
Enable attendance core, then add face recognition for touchless kiosk check-in, alongside QR, IP, and Me portal options — all writing to the same audit-friendly records.
Sites & policies
Configure offices, hubs, and field locations per tenant.
Face recognition
Consent-first enrollment, live match at kiosk or Me, and attendance records with match audit.
HR dashboards
Summaries and site admin tie into the same HR module your teams already use.
Choose how staff prove presence
Start with attendance core, then layer IP, QR, or face modules — each gated in Settings so small NGOs are not overwhelmed.
Sites & records
HR defines attendance sites, allowed methods per site, and stores check-in/out records with worked dates validated against org policy.
Office IP allowlist
Restrict check-in to trusted networks at fixed offices — ideal for HQ where smartphones are not required at a kiosk.
QR kiosk & personal QR
Public kiosk page for supervised sites plus per-staff personal QR payloads from Me portal — no shared passwords on a tablet.
Face recognition
Live face match at kiosk or Me: enroll embeddings once, check in with camera, optional preview ring and match confirmation before POST.
Face recognition attendance
Face recognition attendance
Staff enroll once with consent; kiosks and Me portal run live face match against stored embeddings — then write the same tenant-scoped attendance records as QR or IP check-in.
- Module key `attendance_face` (requires `attendance_core`)
- Stub or HTTP inference client — configure per environment
- Combine with QR on the same site when supervisors want a backup channel
-
1
Enroll with consent
Employees capture a face sample from Me portal or HR-assisted enrollment. Embeddings stay on your tenant; policy controls who may enroll or re-enroll.
-
2
Match at the site
Kiosk or authenticated check-in opens a live camera view, compares the face to enrolled embeddings, and shows match feedback before submit.
-
3
Record & audit
Successful matches create check-in/out rows with worked-date validation — visible to HR alongside QR and IP methods on the same site.
Roll out in the right order
Module dependencies match how NGOs actually adopt attendance: core first, then one channel at a time.
-
1
attendance_core
Foundation
Sites, records, HR attendance admin, and Me attendance APIs.
-
2
attendance_ip
IP restriction
Requires core. Allowlist CIDRs per site for desk-side check-in.
-
3
attendance_qr
QR channels
Requires core. Kiosk route + personal QR generation for staff.
-
4
attendance_face
Face recognition
Requires core. Enrollment APIs, live check-in, embedding compare, and HR-visible attendance records.
-
5
attendance_geo
Geofence (planned)
Reserved for future geofence attestation — not required for today’s pilots.
Built for HQ and field
The same product supports a fixed office, a supervised distribution site, and staff who check in from Me on their phone.
Central office
Enable IP allowlists on HQ sites so check-in only works on office Wi‑Fi, with HR reviewing records in the dashboard.
Field hub · face kiosk
Tablet at a warehouse runs the public kiosk with face recognition — staff look at the camera for match, or fall back to personal QR on the same site.
Staff self check-in
Authenticated Me routes list sites, show personal QR, and post records where privileges and site methods allow.
From site setup to audit trail
Every check-in lands in tenant-scoped attendance records — ready for HR review and operational reporting.
Configure sites
HR admins create attendance sites, set allowed methods, and optional IP rules in the workspace.
Staff check in
Employees use kiosk, IP-bound browser, personal QR, or face — according to site policy.
HR monitors
Dashboards and APIs summarise who was on site, when, and through which channel.
Public kiosk, tenant-safe
The kiosk lives at a dedicated public route — throttled and scoped to your organisation’s sites. Vendors and visitors never see other tenants’ data.
- Public kiosk check-in
- Me portal · personal QR & records
Frequently asked questions
Common questions from NGO programme, finance, and IT teams evaluating this module.
Does the product support face recognition attendance?
Yes. Enable attendance_face after attendance_core. Staff enroll with consent; kiosks and Me portal run live camera match against stored embeddings before writing attendance records.
Is there a public kiosk check-in?
Yes. A public kiosk route supports supervised sites with QR and/or face recognition when those modules are enabled.
Which module should we enable first?
Enable attendance_core first, then add attendance_face for touchless check-in, or attendance_qr and attendance_ip as your sites require.