Punches by hour
today, terminal local timeRecent activity
- No punches yet
Terminal health
Connecting a terminal
what to set on the unit, and what happens nextCurrent modelsSenseFace, SpeedFace, K40 and the like
On the unit: Comm → Cloud Server Setting (some call it ADMS)
- Enable Domain Name
- off
- Proxy
- off
- HTTPS
- on or off, both work
2008-era modelsiClock 360 and the like
On the unit: Setting → Communication setting
- Protocol
- plain HTTP, port 80 only
Find terminals on the network
every address in the range is asked on its management portType the address range of the network the terminals are on, like 192.168.1.0/24 or 192.168.1.10-60; at most 1024 addresses at a time. The port is the units' management port, 4370 on every ZKTeco terminal unless changed on the unit: leave it. The scan runs from this server's own network, so it finds terminals only when the server is on the same network as they are; a server in a data centre cannot see an office. Only units with their management port open can be found and connected from here, without touching the unit. Other terminals must be pointed at this server on the unit itself: Comm → Cloud Server Setting, address , port (2008-era models: Setting → Communication, Web port ). They then appear here under "Waiting for approval".
Waiting for approval
| Terminal | Status | Address | Holds | Record memory | Firmware | Last seen | Actions |
|---|---|---|---|---|---|---|---|
Turned away
these terminals are refused every time they connectDays follow the terminals' clock. "Who is in" reads each person's last punch today: a check-in state means present. Units without state keys report every punch as a check-in, so for them punches alternate: first in, second out, third in.
| Person | Credentials | Role | Group | Terminal | |
|---|---|---|---|---|---|
| Person | Department | Card | Role | On terminals | Fingerprints | ||
|---|---|---|---|---|---|---|---|
Terminals holding this person
what each unit has for themRecent punches
| Time (terminal) | Terminal | Verify | Status |
|---|
Commands about this person
| When | Terminal | Command | Status |
|---|
Details
Credentials in the vault
stored copies, used when putting the person on another unit| Organisation | Branches | Terminals | People | Accounts |
|---|
Terminals waiting for an organisation
| Serial | Firmware | Seen from | Last seen |
|---|
Pick an organisation at the top left to work inside it: its people, terminals, attendance, accounts and settings. A terminal nobody has seen before waits here until it is let into an organisation; one added by serial on the Terminals page belongs to the organisation shown at the time.
| Name | Receives | Last delivery | Queue | Status | |
|---|---|---|---|---|---|
Deliveries
| When | Event | Terminal | Result | Attempt | Next try |
|---|
Each delivery is a JSON POST of the event with headers X-ADMS-Event, X-ADMS-Delivery, X-ADMS-Timestamp and X-ADMS-Signature, an HMAC-SHA256 of "timestamp.body" with the webhook's secret. Anything but a 2xx is retried after 1 min, 5 min, 30 min, 2 h and 12 h, then parked as dead until you replay it.
Console accounts
super admins can change anything; system admins run terminals and people; normal users can only look| Username | Role | Status | Last sign-in |
|---|
| Name | Role | Created | Last used | Status |
|---|
New terminals
for the whole serverWarnings
shown on the Overview page and sent to webhooksTime periods
when a person may punch; the terminal itself refuses a punch outside them| No. | Name | Allowed | People | On terminals |
|---|
Attendance records
Backups
taken per terminal; restore one from the terminal's menuFirmware files
sent to a terminal from its menu on the Terminals page| File | Size | Checksum (MD5) | Uploaded |
|---|