How M1 TimePilot works

From a biometric punch on a ZKTeco device to a payroll line — here is the full flow.

1

Register your company (tenant)

Each company is an isolated tenant with its own employees, devices, branches and payroll. No company can ever see another's data — every record is scoped by tenant.
2

Connect ZKTeco devices (ADMS Cloud Push)

On the device, open Menu → Comm → Cloud Server / ADMS and set:
Server Mode: ADMS
Enable Domain Name: ON
Server Address: device.m1timepilot.com
Server Port: 443 · HTTPS: ON

Devices push punches in real time to one shared endpoint; the platform identifies the tenant by device serial number. No per-device login.

3

Add employees with their numeric machine ID

The employee's biometric PIN from the device is their identity — it matches every punch and syncs enrolment to all of that employee's allowed branches automatically. Unknown PINs are auto-captured so no punch is ever lost.
4

Define Timetables → Shifts → Schedules

A Timetable is one work period (e.g. 09:00–18:00, grace, break). A Shift combines timetables (including weekday rosters and night shifts). A Schedule assigns a shift to an employee over a date range. Night shifts that cross midnight (20:00→05:00) are attributed to a single shift date — never split.
5

Attendance is processed automatically

Each punch is classified (check-in/out, break, overtime). The engine computes worked hours, late, early-out and overtime per shift-date, with manager/HR approvals for manual corrections, leave and OT.
6

Reports & payroll, exportable

Total Time Card, Late-In, Early-Out, Absent, Overtime and Transaction reports — grouped by employee, day or department, exportable to Excel, PDF and CSV. Payroll computes net pay from real attendance (overtime, late penalties, leave) per month.

The four portals

  • 🛡️ Super Admin — tenants, plans, devices, platform reports
  • 🏢 Company / HR — employees, attendance, shifts, payroll, reports
  • 📅 Manager — team attendance & approvals
  • 🙋 Employee — self-service attendance, leave & OT requests

Tenant isolation

Every query is scoped by companyId; devices route in by serial number; employees keep one biometric ID across branches. Each tenant gets its own subdomain (company.m1timepilot.com).