Working time judged by your rules
Set the shift, the grace period, and the absent cutoff per company. On-time, late, absent, and on-leave are all derived in your timezone, never the server's.
- Grace
- 10 min
- Shift
- 08:00 to 17:00
- Timezone
- per tenant
QR and geofence attendance
Staff clock in by scanning a rotating QR, but only inside your office geofence. Roles, leave, and projects included.
Today at Head Office
Asia/Phnom_Penh
Sopheak Chan
Owner
Lina Sok
Manager
Vibol Heng
Staff
Dara Kim
Admin
PK-ERM joins a rotating office code with location validation and company rules, then records the result in one audit trail.
Drop a pin on the map and set a radius. That geofence is the only place attendance counts.
The office QR rotates every 45 seconds. A photographed or forwarded code stops working fast.
We check the signature and GPS distance, then record on-time or late in your timezone.
Set the shift, the grace period, and the absent cutoff per company. On-time, late, absent, and on-leave are all derived in your timezone, never the server's.
The owner toggles permissions to shape the Admin role and any others.
Staff request permission or leave. Approved days never count as absent.
A Kanban board so the same tool covers the work, not only the clock.
Shared schema with a company id on every row, plus Postgres row-level security.
Browser GPS can be faked by determined users. PK-CRM layers rotating codes, accuracy gating, and a full audit trail so disputes are resolvable.
Tenant-scoped data access plus Postgres row-level security keyed on the session company.
Each code is an HMAC of the zone and a short time window, so shared codes expire quickly.
Coarse GPS fixes are rejected, and every scan attempt is logged for disputes.
Set your hours, draw your zone, invite your team, and start scanning.