Register an attendance machine

What this achieves

Registering a device tells Humavera which terminal is allowed to send punches and how to recognise it. Until a device is registered, punches from it are not accepted.

Required role: Administrator.

Before you start

Have the serial number from the device itself to hand. It cannot be changed after registration, and the punches already received are tied to it.

Steps

Go to Time & Attendance → Attendance Machines.
Select Register machine.
Enter the Name.

Example: Warehouse Gate.
Enter the Serial number exactly as printed on the device.
Choose the Protocol.
Enter the Location label.

Example: London — main entrance.
Set the Device timezone.
Under Security, set Require the ingest token, Require an API key, and Allowed source IPs.
Set Active.
Select Register.

The token appears once

Registering issues an ingest token, and it is shown immediately afterwards. The screen states the limit of that: this is the only time it is displayed, it is stored encrypted, and it can never be shown again.

Copy it before closing the dialog. If it is lost, the way to get another is to remove the machine and register it anew.

Options on this panel

Option	Description
Name	What the device is called in your list.
Serial number	How the terminal identifies itself. Entered exactly as printed on the device, and fixed after registration.
Protocol	The protocol the terminal speaks. The picker names which terminal families each option covers.
Location label	Where the device is, for the people reading the list.
Device timezone	Recorded for reference.
Require the ingest token	The device must present its token for a punch to be accepted.
Require an API key	The device must present a key as well.
Allowed source IPs	Addresses punches are accepted from, separated by commas. Left empty, any source address is accepted.
Active	Whether the device is currently accepted.

Set the terminal to UTC

The timezone you record here is held for reference. Punch times are read as UTC, and the screen says so where you set it.

Set the device itself to UTC. A terminal running on local time delivers punches shifted by its offset, and nothing flags them — they arrive looking entirely ordinary.

Example: a terminal at the London site left on local summer time records Tom Hargreaves arriving at 08:00 as 09:00. His day looks an hour short and no error is shown anywhere.

The security controls

The three security settings decide what Humavera will accept as a genuine punch from this device. A device requiring neither a token nor an API key, with no address restriction, accepts punches from any source that can reach it.

Set them with whoever runs your network. What each one does is described above; how your network should be arranged is a decision for your own IT team rather than something this documentation can settle.

Editing a registered device

Edit reopens the same panel to update how the device is identified and secured. The serial is the exception and is locked, with the reason stated on screen.

Removing a device

Remove asks you to confirm and states what it does: punches already recorded are kept, and the device stops being accepted from that point.

Removing is therefore safe for the attendance history and final for the device. A terminal removed and reinstated has to be registered again, with a new token.

What happens next

A registered device appears in your list with its last-seen time, showing as never connected until its first punch arrives. Hand its setup details to whoever configures the terminal, then watch the device record to confirm punches are arriving.