Lakshya

Org chart

Reporting hierarchy. Click ▸ to expand a manager's direct reports; click a name to open their detail tab. Default expansion is 2 levels — your last expand/collapse state is remembered per-browser. Filters dim non-matching nodes (the tree shape stays so you can still navigate around).

Schedule vs productivity

Compares actual productive time against the expected time defined by each employee's shift. Ratio is weighted (uses the bucket weights from Manage → Bucket weights), so e.g. learning time partially counts. Holidays / weekends / admin-marked exempt days have expected = 0 and don't drag the average down.

Best & worst — last 7 days

Score = (productive + 0.5×learning − personal) ÷ active time, mapped to 0–100. Excludes employees with under 10 minutes of activity in the window. Security-risk time is shown separately as alerts — not deducted.

Auto-groups — last 14 days

Rule-based, transparent. Each membership shows the reason — useful for defending decisions in 1:1s.

Needs review

Apps, domains, and browser titles that have accumulated active time but aren't classified into a bucket yet. Tag them here once and they apply retroactively to every employee.

My data

Your own activity at a glance.

System health

Audit log

Every privileged action — grants, revokes, role changes, category re-tags, OMS syncs, retention runs.

Integrations

Responsibilities & delivery

Alerts

Active RDS thin-client sessions (Windows 2012)

Maps server\session_id -> AD user -> employee record.

Employees — Windows login mapping

The OMS Windows login column is what your OMS reports (LOWER(sec_users.login)). The Override column is a manual mapping — useful when an employee's actual Windows account name doesn't match the OMS login (e.g. administrator, service.user). Override wins during agent matching and survives OMS re-syncs.

Windows agent — build & deploy

Download these files to a Windows machine, run the build script, then install the resulting empmonitor_agent.exe on each RDS host. The agent reports back to ….

# 1. On a Windows machine with Python 3.9+ in PATH:
Set-ExecutionPolicy -Scope Process Bypass
.\agent\build_windows.ps1
# Output: dist\empmonitor_agent.exe

# 2. On each RDS host, copy the exe + install_agent.ps1, then as Administrator:
.\install_agent.ps1 -ServerUrl "http://192.168.0.131:8090"
# Agent now starts at every user logon and reports its session to this server.

Category rules

Shifts

Recurring time windows that define expected on-the-clock hours. Each employee inherits the default shift unless overridden on the Employees page. Productivity ratios on the Schedule dashboard use these windows.

Each shift now belongs to an office (or company-wide if blank), and has an effective from date. When computing for an employee on a given day, the system picks the most-recent active shift for their office whose effective_from ≤ that day, falling back to the company-wide shift if none.

Holidays

Days where expected_s is forced to 0 — so the productivity ratio reads as "off-day" rather than 0%. Leave Office blank for company-wide holidays; otherwise it must match the Employee.office string (e.g. Udupi).

Title keywords

Maps a substring in a browser-window title to its canonical domain. Used by the title extractor to recognise sites like "Stack Overflow - Where Developers ..." → stackoverflow.com. Higher priority is checked first; keep more-specific keywords above generic ones.

Office settings

Per-office effective_date — the date from which monitoring is "live" in that location. Days before this date are excluded from expected_s and from auto-leave for employees in that office. Offices with no row here use the global default on the System settings page.

Add a new office

Use this only for offices not yet on any employee record. Otherwise the office is auto-listed above.

System settings

Configuration that affects how the productivity ratio is computed across the company.

Flagging thresholds

Two independent rules. Each can fire on its own — an employee can be flagged for unproductive use, for excess idle, or for both. Changes take effect on the next recompute (overnight, or run a manual recompute from Health).

Bucket weights

Weights applied to every second of activity time when computing the daily productivity score. Negative weights deduct (e.g. personal). Typical range is -1.0 to +1.0; nothing rejects values outside that range — pick what makes sense for your formula.