Biometric devices
Schools that capture attendance at a gate or a staff-room door register their readers under Attendance → Devices. Once a device is registered and its users enrolled, it posts attendance into ShuleOne without anyone marking a register.

The device screen lists registered readers or starts device enrolment when none exist.
Registering a device
Section titled “Registering a device”Select Add New and record:
| Field | Notes |
|---|---|
| Device name | Where it is — “Main gate”, “Staff room”. |
| Serial number | From the device itself. This is what identifies it when it reports in. |
| Location | Used on reports to tell two readers apart. |
| Applies to | Students, staff, or both. |
| Session | Whether a scan marks arrival, departure, or both by time of day. |
The device needs a network connection to reach ShuleOne. If a reader stops reporting, check the network before assuming the device has failed — it is the cause far more often.
Enrolling users
Section titled “Enrolling users”A device recognises a person by a fingerprint or a card enrolled against their ShuleOne record. Enrolment happens at the device and matches on the staff number or admission number, so those must already exist and be correct.
To send existing people from ShuleOne, open Attendance → Devices, choose the people and destination reader, then select Send to gadget. A school opening this workflow for the first time receives the standard attendance settings automatically; no settings setup is required before the send.
When two campuses share one physical reader, its user IDs form one combined list. The same admission or biometric ID cannot identify different people at the two campuses. ShuleOne refuses a conflicting send instead of overwriting the person already on the reader. Give one person a different biometric ID, remove the stale user from the reader, and send both records again.
A scan from someone who is not enrolled is recorded as unknown rather than being attached to a guess. Unknown scans are worth reviewing occasionally — they are usually an enrolment that did not complete.
Live capture and manual marking together
Section titled “Live capture and manual marking together”Device capture and manual registers coexist:
- A student scanned at the gate is marked present automatically.
- A class teacher can still open the register and correct it — a learner who arrived before the reader was working, for example.
- Manual corrections win over the device, and are recorded as amendments.
This matters on the days a reader fails. Attendance does not stop; the class teacher marks the register by hand for that day.
What to check when a device seems wrong
Section titled “What to check when a device seems wrong”| Symptom | Where to look |
|---|---|
| Nobody appears from a device | Network, then the device serial number in ShuleOne. |
| One person never registers | Their enrolment, and whether their staff or admission number matches. |
| A shared reader refuses one person | Check whether another campus uses the same admission or biometric ID on that reader. |
| Everyone shows as late | The clock on the device, and the late cut-off in attendance settings. |
| Duplicate scans | The device is set to mark both arrival and departure; check the session rule. |
| Scans arrive hours later | The device has been offline and is uploading a backlog. This is normal after an outage. |
Transport devices
Section titled “Transport devices”Vehicle-mounted readers used to record who boarded a bus are managed separately under Transport → Devices, because they answer a different question — who is on the bus — rather than who is in school.
