Team IST
| Member | Status | Scheduled | Arrived | Left | Active | Span | Offline appr. | Credited | App mix |
|---|
Present means "recorded presence that day", not "full day" — the compliance rules (<4h etc.) apply downstream. Span = first→last active (the fair “were you here” number). Active = measured interaction. Credited = active ∪ approved offline, counted once. App mix is from the foreground app name only (tabs/URLs never read) — a hint, not the attendance number. Per policy, Super Admins and on-site client-project members are excluded from tracking (same rule as DeskTime).
Team active hours by day
Per-member totals
| Member | Days present | Active | Avg active / present day | Offline appr. | Credited | Category mix |
|---|
Day timeline IST
Per-minute dominant app category — app name only, tabs/URLs never read. Gaps are idle or away time, not misconduct.
Category mix
Top apps app name only
| App | Active time |
|---|
Last 14 days — active hours
Offline-time approvals
Member-declared off-machine time (meetings, office visits, travel, WFH). Approving credits it toward that day’s presence — overlap with measured activity is never double-counted.
| Member | Date | Time (IST) | Kind | Duration | Note | Status | Action |
|---|
Absence calendar
Approved leaves from Organized — requests and approvals stay there; this is a read-only reflection. Weekend shading follows the default schedule.
Work schedules
Shift window + grace drive Late; scheduled working days drive Absent. Members without an override use the default . Shifts must start and end on the same IST day — overnight shifts aren't supported yet, so don't assign one (it would generate false Absents).
| Member | Shift (IST) | Grace | Working days |
|---|
Set / override a schedule
Reports & export
Per member per IST day: status, late, arrival/left, measured active, span, approved offline, credited presence, and the app-category minutes. CSV cells are formula-injection-guarded. Days before 1 Aug 2026 with no agent data show archived DeskTime hours (hours only — no app mix or arrival times existed).
Captured apps everything seen so far
Every foreground app name the agents have captured, with the category it currently resolves to. Tick apps and mark them — each becomes its own exact rule (which outranks the generic seeded patterns) and applies to all history at read time.
| App | Category | Active time | Matched rule |
|---|
App categories productivity policy
How foreground app names map to productive / neutral / unproductive (longest match wins; unmatched = neutral; no app name = unknown). Edits apply to all history at read time. The mix is a hint — how names map to categories is company policy set here; anything unmatched reads neutral (tabs/URLs are never captured).
| Pattern | Category | Updated by |
|---|
Enrolled devices
| Member | Host | OS | Agent | Enrolled | Last seen | Status |
|---|