Accurate timekeeping, privacy-safe activity signals, schedules, attendance and payroll-ready reporting inside the governed Varajen workforce platform.
Varajen Time connects collection, policy, coverage, review and deployment controls so teams can understand both the metric and the evidence behind it.
Tracked, active, idle, meeting, manual and unverified time remain distinct. Coverage stays beside every metric, and missing information is never silently converted to zero.
Measure verified foreground applications and normalized active website hostnames without collecting page content, typed text, passwords or background-tab activity.
Connect individual and team schedules, time zones, attendance review, timesheet approvals and payroll-ready summaries without confusing schedule compliance with productivity.
A visible Windows agent, supervisor, encrypted durable queue, idempotent ingestion and component health help preserve data through restart, sleep and temporary network loss.
When explicitly enabled, protected screenshots follow tenant policy, sensitive-surface exclusions, short-lived viewing access, audited actions and limited retention.
Discover and preview eligible Entra users, prevent duplicate invitations, restrict imported roles and preserve historical records through administrator-controlled workflows.
See when tracking is active, review permitted personal time and understand exactly what the organization collects.
Review authorized team time, schedules, exceptions and source coverage without crossing assigned access boundaries.
Use reviewed timesheets, attendance context and exports as controlled inputs to workforce and payroll-readiness workflows.
Manage policy, enrollment, endpoint health, retention, directory imports and audited deployment controls.
No. It can record aggregate keyboard and mouse event counts for activity measurement, but not individual keys, typed content, passwords, clipboard contents or raw pointer coordinates.
Not by itself. Attribution is based on verified foreground intervals. Background-open applications and inactive browser tabs are not treated as active work.
Pending endpoint records remain in an encrypted local queue and retry after connectivity returns. Sequence-aware processing reduces duplicate ingestion, while reporting continues to expose coverage gaps.
No. Screenshot collection is optional and disabled unless tenant policy enables it. When enabled, exclusions, protected storage, short-lived access, audit events and configured retention apply.
No. Portal actions require a future endpoint heartbeat. Out-of-band repair or power management requires Microsoft Intune or another approved endpoint-management platform.
