Workforce combines people, devices, application usage, website-hostname activity, active and idle time, classification and daily reporting in a customer-scoped SaaS workspace. It is currently in controlled production finalisation, not unrestricted paid production.
Attendance management, shifts, screenshots, AI features, self-service billing, guaranteed retention and public code-signed installation are not included in the current launch scope.
Maintain employees and departments, create customer administrators, and optionally assign managers to approved departments or employees through a formal permission matrix.
Use agent heartbeat data to review active and idle status, foreground applications, registered devices and website hostnames collected through the browser connector.
Classify applications and website domains with company rules and review productivity signals as operational context. Workforce does not make disciplinary decisions.
Use the Reports Hub, Daily Work Reports and Activity Evidence views with company-scoped filters. CSV, PDF, email and scheduled delivery remain entitlement and configuration dependent.
Use company-scoped installation tokens, authenticated agent submissions and Windows identity mapping. The installer and connector packages must pass the controlled release process before customer deployment.
Authorised platform administrators can assign database-defined packages, customer limits and module overrides, while selected administrative actions are recorded in product audit logs.
The official connector reports the active focused tab hostname to the installed agent. Workforce does not present screenshots or page content as evidence.
Review security approachActive browser hostname only
No full URL paths, query strings or fragments
No page titles, page content or browser history
No typed text, keystrokes or clipboard capture
No screenshots, screen recording or live screen viewing
No webcam or microphone collection
Controlled pilot proposals may be prepared manually after the required modules, limits, deployment method, retention responsibilities and support boundaries are agreed. No website package table overrides the application’s approved catalogue.