For teams running managed Windows machines
TeamLens
Available nowWorkforce visibility, activity tracking and team reporting.
Rather be shown than sign up? Ask, and we will walk you through the app on a call and answer as we go. It is booked by email — we do not embed a scheduling widget.
TeamLens watches enrolled Windows machines and reports on what it sees: which applications are in use and for how long, when someone signed in and signed out, how much of the day was active, what software is installed and what changed, and USB activity. It raises alerts against rules you configure, and reports by person, by department and across the organisation.
It needs a small agent on each machine. You download an installer from the Devices screen, run it once, and the machine appears in the fleet. Agents check in about once a minute and pick up a policy change on their next check-in, so turning a capture off takes effect within about a minute rather than at the next reboot.
Screenshots are the sensitive part, and they are treated that way. They are captured on the interval you set in Policies, opening one is recorded against the name of the person who opened it, and the link that shows it stops working five minutes after it is created.
There is also anti-cheat detection — signals that input is being automated or that monitoring is being evaded, from auto-clickers and mouse jigglers to remote-desktop sessions and virtual machines. It reports and nothing more: no process is ended and no device is blocked.
This is a product that watches people. We would rather say that on the page than have you find it out from an employee, so the whole of what it captures is listed above, and the things it deliberately does not do are listed below.
Who this is for
TeamLens is built for a particular kind of desk.
If none of these is you, it is probably the wrong app — and we would rather say so here than after you have set it up.
Managers of distributed teams
Your people work on company machines you do not stand next to, and you would rather have a measurement than an impression.
Operations and IT
You want to know what is installed across the fleet, what changed, and which machines have stopped reporting.
Anyone who has to justify the hours
You bill or report on time and would rather it came from a record than a reconstruction.
Teams with a real integrity problem
You have reason to believe activity is being faked, and you want the signal rather than an argument.
What it covers
Inside TeamLens
Activity, sessions and working hours
Application use categorised as productive or not, active against idle time, and hours measured against the schedule that applies to that person or department.
Screenshots, held carefully
Captured on the interval you set. Opening one is recorded against the viewer's name, and the link expires five minutes after it is created.
Alerts and anti-cheat signals
Rules you configure, checked every minute, with repeat alerts backed off rather than repeated. Seventeen kinds of automated-input and evasion signal, reported and never acted on automatically.
Every screen
The whole of TeamLens, not the highlights.
These are the app's own sections and the 14 screens inside them — the same names you will see in the navigation once you are signed in.
Fleet
- Overview
- Whether the machines you expect to be reporting are reporting.
- Devices
- Every enrolled device, with the active badge following a sign-in or sign-out within about a minute. The installer is downloaded from here.
- Software
- What is installed across your enrolled devices, and what has been installed or removed since the last scan.
Activity
- Timeline
- Everything one device did, in the order it happened: sign-ins, applications, screenshots and anti-cheat signals on one line.
- Screenshots
- Captured on the schedule set in Policies. Opening one is recorded against your name, and the link expires five minutes after it is created.
- Applications
- Every application seen, and whether it counts as productive — which is what lets every other report separate work from everything else.
Detection
- Alerts
- Rules you configure, checked every minute, with a repeat alert backed off to daily and then to once rather than arriving every hour.
- Anti-cheat
- Devices showing signs of automated input or of monitoring being evaded. TeamLens reports these and stops nothing.
Workforce
- Departments
- Group people into departments, so a schedule or a report can apply to a team rather than a person at a time.
- People
- Who in the organisation can open TeamLens, and what they may see.
- Schedules
- The hours that count as working hours for each person, and which level decided them. Off-hours and idle alerts are both measured against these.
- Reports
- Productivity, application use, web activity, time buckets and exceptions — exported on demand or emailed on a schedule.
Configuration
- Policies
- What the agent captures, how often, and what it leaves alone — screenshot frequency, idle thresholds, anti-cheat scanning and working hours. Enrolled devices pick up a change on their next check-in.
- Settings
- Data retention, access control and the policies that apply across the organisation.
Before you install
What we would rather you heard from us.
Every product page is written by someone who wants you to buy it. These are the parts that argue the other way, and they are here on purpose.
Windows only, and it needs an agent installed
TeamLens watches enrolled Windows machines through a small program installed on each one. There is no macOS or Linux agent, and nothing is captured from a machine that has not been enrolled.
The installer is not code-signed yet
Windows will show an unknown-publisher warning when somebody runs it. We have not bought a code-signing certificate. It is on the list, and until it is done you should expect that warning and tell your people to expect it too.
Telling your people is your job, and it matters
This software watches people. What you are required to tell employees, and what consent you need, depends on where they work and how they are employed — it is not something we can decide for you, and we will not imply that installing it settles the question.
Who can see what is restricted, deliberately
Activity and screenshots are behind their own permission. Somebody who administers your CloudVersa organisation but has not been given that permission in TeamLens sees none of it.
Pricing
What TeamLens costs
The organisation account is free. TeamLens is priced per seat — you pay for the people you give it to, and nobody else.
The organisation is free
Creating your company on the platform costs nothing, whether or not you install an app. There is no platform fee and no bundle to buy.
Each app is priced per seat
You give an app to the people who need it, and each of those is a seat. A company of forty with six people in an app pays for six.
Every app has its own plans
An app sets its own tiers, because what separates them differs by app — a document volume in one, a part of the product in another. The marketplace shows you the plan before you install anything.
Prices are quoted, not published
What a seat costs and what each tier includes depends on the app and on how your firm is set up, so we would rather tell you than have you work it out from a table that is still moving.
30-day trial, then a plan. Installing TeamLens starts the trial: the whole app, for your whole organisation, with no card required to begin it. When the 30 days are up you choose a plan. Until you do, the app stops opening — everything created during the trial is kept and is still there when a plan is chosen.
Prices are quoted, not published. What a seat costs and what each plan includes depends on the app and on how your firm is set up, so we would rather tell you than have you work it out from a table. Ask us what it would cost and a person will answer.
Fair use applies. A seat is priced for one person doing their job. If an organisation’s use is well beyond what its seats would normally produce, we talk to you first and agree a plan that fits — with 30 days’ notice before anything changes. Read the fair use policy.
Questions
What people ask about TeamLens
What exactly does TeamLens capture?
Application use and the active window, sign-in and sign-out events, active against idle time, periodic desktop screenshots on an interval you set, installed-software inventory and what changed, USB insert and remove events, and signals that input is being automated or monitoring evaded. Everything it captures is configured in Policies and can be turned off there.
Does it work on Mac?
No. The agent is Windows only. A machine without the agent installed is not watched at all.
Who can look at the screenshots?
Only people you have given the activity permission to inside TeamLens — being an administrator of your CloudVersa organisation is not enough on its own. Opening a screenshot is recorded against the name of the person who opened it, and the link that displays it expires after five minutes.
Does the anti-cheat detection block anything?
No. It reports. No process is ended, no device is blocked, and nothing is decided automatically — the signal goes to a person.
Do we have to tell our employees?
That depends on where they work and how they are employed, and it is a question for your own advisers rather than for us. What we will say is that we have built the product on the assumption that you will: the capture settings are explicit, viewing a screenshot is logged against the viewer, and access is restricted by permission rather than by seniority.
What does TeamLens cost?
The organisation account is free. TeamLens is priced per seat, and every app starts with a 30-day trial. Ask us and we will tell you where its plans stand.
Do we need a separate login for each app?
No. That is the point of the platform. A person is added to your organisation once and signs in at accounts.cloudversa.io for every CloudVersa app they have been given. Removing them removes their access everywhere.
Can we get our data back out?
Yes. The information your organisation puts into an application stays yours. If you stop using CloudVersa, ask us and we will give you a copy of your data in a reasonable format before it is removed — that is written into the terms of use, not left to goodwill.
Something not answered here? Ask us — a person reads it.
Coming off a spreadsheet?
Most firms moving to TeamLens are not leaving a competitor — they are leaving a spreadsheet, a shared drive and an inbox. We have written down where each of those stops, what a move involves, and how to get your data back out again.