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.

OMS customers

Customers mirrored from the OMS Implementation Report. Assignments shown are currently active (excluding history). Empty until OMS pushes data via the webhook configured on Manage → Integrations.

tldv meetings

Each tldv-recorded meeting with its company participants and all action items extracted. Most-recent first.

tldv action items

Action items that tldv extracted from recorded meetings, awaiting admin review. Approve to create a Responsibility for the assigned employee, or dismiss if not actionable.

Monthly assessments

Rate each of your direct reports 1–5 for the month, with optional comment. Feeds the manager component (15%) of the composite score. Submit by the 5th of the next month for cleanest data — late submissions still count, but holders may have already seen draft rankings.

Ratings: 1 below expectations · 2 needs improvement · 3 meets expectations · 4 exceeds · 5 exceptional

Monthly ranking

Composite employee score combining productivity (30%), delivery (25%), and four other components that will fill in as subsequent phases ship (manager assessment 15%, customer outcomes 15%, peer nominations 10%, tldv follow-through 5%). Components with no data are skipped — the score re-normalises over the available ones.

Positions

Job profiles per role. Every employee sees their role's profile on My Data. Empty entries (unfilled) show roles with employees but no profile written yet — click Edit to author one.

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

/v1/tldv/webhook

/v1/oms/webhook

Responsibilities & delivery

Leave types

The dropdown on the Leaves page reads this list. Add a new type here (e.g. Paternity, Bereavement) and it appears in the form immediately. Deactivate a type to hide it from new entries without losing the historical leaves that used it.

Reassign activity

Move all activity events from one employee to another for a date range. Useful when someone covered for a colleague on their machine. Preview first — the move overwrites the attribution and is logged to audit trail, but original employee_id is NOT preserved per-event.

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, bundle & deploy

Build the EXE + bundle it into a single self-contained Install-Lakshya.ps1 on a Windows box (once). Copy that one file to each target machine. The agent reports back to ….

$cookie = (Invoke-WebRequest "https://lakshya.pcs-india.com/v1/auth/login" -Method POST `
    -Body (@{username='YOUR_ADMIN_USER'; password='YOUR_PASSWORD'} | ConvertTo-Json) `
    -ContentType "application/json" -SessionVariable s).BaseResponse

Invoke-WebRequest "https://lakshya.pcs-india.com/v1/admin/install-bundle" `
    -Method PUT `
    -InFile "C:\empmonitor\agent\Install-Lakshya.ps1" `
    -ContentType "application/octet-stream" `
    -WebSession $s

.\Install-Lakshya.ps1 -ServerUrl "…"

irm …/install.ps1 | iex

# On any Windows machine with Python 3.10+ in PATH:
Set-ExecutionPolicy -Scope Process Bypass
.\agent\build_windows.ps1      # produces dist\empmonitor_agent.exe (~12 MB)
.\agent\bundle_installer.ps1   # produces agent\Install-Lakshya.ps1 (~16 MB)

# Then upload empmonitor_agent.exe to this server (so the one-liner above
# can serve it) via PUT /v1/admin/agent-binary, and ship Install-Lakshya.ps1
# to each target.

cd C:\Temp

Set-ExecutionPolicy -Scope Process Bypass

Add-MpPreference -ExclusionPath C:\ProgramData\EmpMonitor
Add-MpPreference -ExclusionProcess empmonitor_agent.exe

.\Install-Lakshya.ps1 -ServerUrl "https://lakshya.pcs-india.com"

.\Install-Lakshya.ps1 -ServerUrl "http://192.168.0.131:8090"

whoami

Get-Process empmonitor_agent | Select Id, SessionId, UserName

Get-Content C:\Users\<user>\.empmonitor.json

Get-Content C:\Users\<user>\AppData\Local\empmonitor\agent.log -Tail 10

Get-Process empmonitor_agent | Stop-Process -Force
Remove-Item C:\Users\<user>\.empmonitor.json -Force
Start-ScheduledTask -TaskName "EmpMonitor Agent (system-wide)"

Start-ScheduledTask -TaskName "EmpMonitor Agent (system-wide)"

cd C:\Temp
.\Install-Lakshya.ps1 -Uninstall

Installed agents

Every machine running an agent registers a unique agent_key on first start. Once the key is bound to an employee, that binding is locked — events from that key are only attributed to that employee. To swap a stolen or stale install, revoke the row here and reinstall on the host.

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).

Security policy

Hardening controls. Changes take effect immediately on the next request — no restart needed.

Password requirements

Applied to every password change and reset. Existing passwords stay valid until the next change unless maximum age below forces rotation.

Sessions

Account lockout

Webhook destinations

Comma-separated allow-list of hostnames. Empty = any URL accepted (insecure on a public deploy — webhook URLs become an SSRF surface). Set to e.g. hooks.slack.com,n8n.example.com to restrict.

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.