Team leads sit between the people doing the work and the people who set policy. In Kyrospect, an Owner can give a lead a custom role limited to their team, so they see what they need and nothing more.
What a lead can see
- Shift start, end and duration; active and idle time (Track Basic).
- On Track Advanced or Advanced+: app and window activity, URL context and screenshots at the workspace's interval, with privacy blur if the workspace enables it.
- The team's people records within the permissions the role grants.
Every employee can see their own records — the same data their lead reviews. That symmetry is deliberate.
A weekly routine
- Look at patterns across the week, not single days.
- Note anomalies as questions, not conclusions.
- Raise them in a one-on-one with context — see conversation-first review.
- Fix systemic issues (meetings, unclear priorities) before individual ones.
Questions team leads usually ask
Can I see other teams?
Only if the role an Owner assigns you allows it. Scope roles to the team a lead actually manages.
What do I say when someone asks why tracking exists?
Point to the written policy and the purpose behind it, and remind them they can see the same records you can. If you cannot explain the purpose, raise that with whoever set the policy.
Can I change capture settings?
Capture intervals and privacy blur are workspace policies set by the Owner, not individual lead choices, so the rules stay consistent.
What not to do
- Do not rank people by activity percentage — it is a weak measure of output. See why activity percentage is a weak KPI.
- Do not use screenshots as a live feed.
- Do not act on automation-pattern signals (preview, Windows only) without a human review and a conversation.
More on leading distributed teams: remote leadership guides.