Fingerprint synchronization
Employees enrol their fingerprints on a TimeLok recorder. Fingerprint synchronization reads them from that recorder and copies them to the company's other recorders, so each employee enrols once instead of on every device.
Fingerprint synchronization is activated separately for each client and is off by default. To use it, contact support at [email protected]. Until it is activated, the settings described below are not shown.
Before you activate it, check whether you may use biometric data for time tracking: see Biometrics and GDPR.
Turning it on
- Ask support to activate fingerprint synchronization for your company.
- Open Settings and find the Fingerprint synchronization card.
- Tick I authorize central fingerprint storage and synchronization for this company and click Save.
From then on BeepClock works in the background:
- When an employee enrols a fingerprint on a recorder, BeepClock reads it and delivers it to the other recorders.
- A recorder that is offline receives the fingerprints when it reconnects.
- Locations do not limit synchronization: every recorder of the company takes part unless you exclude it.
- Fingerprints are stored in BeepClock in encrypted form, separately from other data.
Enrolment itself still happens on the recorder. A fingerprint belongs to the employee with the same number on the recorder and in BeepClock.
Excluding a recorder
Open the recorder in Devices and tick Exclude from fingerprint synchronization. The change is saved immediately. An excluded recorder neither supplies nor receives fingerprints. Fingerprints already on it stay there, and Remove fingerprints everywhere still includes it.
An employee's fingerprints
The Fingerprints tab on the employee card shows the fingerprints BeepClock knows about. Each one is listed under its number on the recorder (Fingerprint number 0 to 9), followed by its state on every recorder. Refresh loads the current state.
After a change, the tab shows Change saved. Devices are updated in the background and this view refreshes automatically. While a delivery, a removal or a new enrolment is still running on a recorder, it shows Synchronizing with devices. This view refreshes automatically. and reloads every few seconds until the recorders have finished. Refresh is only needed to check straight away.
The state next to the fingerprint number:
- Accepted: BeepClock holds this fingerprint and delivers it to the recorders.
- Empty: BeepClock holds no fingerprint under this number.
- Conflict: recorders hold different fingerprints; choose one, see Conflicts.
- Pending, later Removed: a removal is running; Removed once every recorder has confirmed it, see Removing fingerprints.
| State on a recorder | Meaning |
|---|---|
| Synchronized | The fingerprint is on this recorder. |
| Pending | A delivery or removal is waiting, for example because the recorder is offline. |
| Not enrolled | The recorder has no fingerprint under this number. |
| Deleted locally | Someone deleted the fingerprint directly on this recorder. BeepClock respects that and does not send it back to this recorder. |
| Removed | The fingerprint was removed with Remove fingerprints everywhere. |
A short message under a recorder explains a delay, for example Device offline; waiting for reconnection.
Conflicts
If recorders hold different fingerprints under the same number for one employee, BeepClock does not choose between them. That fingerprint is marked Conflict and is not delivered until you decide:
- Use followed by a recorder name takes the fingerprint from that recorder.
- Keep current fingerprint keeps the fingerprint BeepClock already holds.
Removing fingerprints
Remove fingerprints everywhere on the Fingerprints tab:
- deletes the employee's fingerprints stored in BeepClock straight away,
- asks every recorder of the company to delete them, including excluded and offline recorders,
- keeps the employee's cards, PIN codes and attendance records.
Offline recorders delete the fingerprints when they reconnect. If a fingerprint on a recorder has changed since BeepClock last read it, or BeepClock cannot confirm it is the same one, the removal stays Pending instead of deleting it blindly. In that case delete the fingerprint directly on the recorder. A command already sent to a recorder cannot be recalled.
While a removal is pending, BeepClock does not import new fingerprints of that employee.
Enrolling again after removal
When every recorder has confirmed the removal, the tab asks for a new enrolment:
- Enrol the employee again on one recorder.
- Choose that recorder in Enrollment device.
- Click Confirm new enrollment.
BeepClock reads the fingerprints from that recorder and resumes synchronization. A notification from the recorder alone does not prove the enrolment is new, which is why the confirmation is required.
If a removal is still pending and you want to keep fingerprints that were enrolled in the meantime, choose their recorder and click Keep fingerprints and resume synchronization. This cancels the pending removal. Fingerprints left on other recorders are not deleted automatically, and different ones become conflicts.
Turning it off
Untick the consent in Settings and click Save. Synchronization stops, and the fingerprints stored in BeepClock are deleted together with their encryption key. Fingerprints already on recorders stay there. If they should disappear from the recorders too, use Remove fingerprints everywhere for each employee before turning synchronization off.
Permissions
If your organisation uses roles, giving or withdrawing consent requires Change settings, excluding a recorder requires Edit devices, and resolving conflicts, removing fingerprints and confirming a new enrolment require Edit employees.