SiteTime Sign In
Connecting securely to SiteTime service…
Test accounts
Worker: afzrahman
Manager: manager1
Worker: afzrahman
Manager: manager1
TAYSAR SiteTime
Welcome
Loading workspace…
Simple attendance workflow
Today—Attendance status
Pending Approval0Waiting for manager decision
Approved Hours0.00 hCurrent month validated hours
Simple flow: Clock IN → Clock OUT → Manager approval → Timesheet.
--:--
Demo Worker • 10027
Current state
Checking…
Checking…
Device AuthenticatorNot registered
LocationNot captured
GPS Accuracy—
Latest Approval—
Shared V0.3: Clock In/Out is written to Cloudflare D1 through the Worker API. Reporting Manager sees the same record on another device.
Pending Approval0
Approved0
Rejected0
Returned0
Loading team shift status…
Manager Approval Queue
Approval is available only after a worker completes both Clock IN and Clock OUT.
| Worker | Site | Clock IN | Clock OUT | Hours | GPS / Boundary | Status | Action |
|---|
Shared Attendance Audit History
| Worker | Type | Timestamp | Site | GPS | Authentication | Status | Decision |
|---|
Timesheet
Only approved and validated shifts are included in final hours. OT is calculated after the 9-hour elapsed shift rule and remains subject to manager approval.
Present Days0
Validated Shifts0
Total Hours0.00
Regular Hours0.00
OT Hours0.00
Pending0
Shift rule: 9 elapsed hours including 1-hour lunch = 8 regular hours. OT starts after 9 elapsed hours.
Approved Shift Details
| Date | Worker | Site | IN | OUT | Elapsed | Net | Regular | OT | Status |
|---|
Profile
Name—
User ID—
System Role—
Designation—
Reporting Manager—
Device Authentication—
Keep it simple: role controls access; designation is only the employee's job title.
V0.3 Security Boundary
Shared database: attendance records are now sent to a Cloudflare Worker API and stored in D1.
Authentication: demo login is validated by the Worker and a signed short-lived session token is returned.
Biometric: Face ID/fingerprint/Windows Hello stays inside the operating system. This prototype invokes WebAuthn locally. The V0.3 backend records the client verification result, but does not yet perform production-grade WebAuthn assertion verification. That is the next security hardening step.
Location: Phase 1 captures GPS only at attendance events. No continuous tracking.
Production requirement: restrict API CORS to the production Pages domain, use corporate SSO, verify WebAuthn server-side, add device enrollment/revocation and formal data-retention controls.