Time tracking with screenshots, and an honest list of who is not being captured

An admin switches screen capture on for the organisation and sets one capture interval, anywhere from 10 seconds to 60 minutes, entered in seconds or minutes. When the switch is off, no screenshots are taken for anyone. When it is on, a member who checks in is asked by their browser to share their screen. They choose the entire screen, an application window or a browser tab, and each screenshot records which of the three it was.

The browser asks once per session, not once per screenshot: AMS keeps the shared screen open and takes a frame at each interval, then uploads it from the browser straight to your organisation’s storage. Capture follows the clock. On a break, during a manual pause or while the idle policy has paused the timer, no frames are taken — and when work resumes the next frame is taken straight away rather than a full interval later.

Capture does not have to be all or nothing. Under Per-Employee Exceptions an admin ticks the people who are excluded regardless of the organisation-wide setting — a director, a contractor whose agreement rules it out, someone who works on a client’s machine. An excluded person is not prompted to share their screen when they check in. The list is searchable and paged, and changes are applied together with one button, so a half-edited list is never live.

Who may see and change these settings is a permission, not a fixed role. Viewing the screenshot policy and updating it are separate permissions, so you can let a team lead read the policy without letting them change it.

Every member has My Screenshots: their own frames, day by day, with no permission needed. Nobody has to wonder what was taken of their screen, because they can look.

Team Screenshots is for the roles you grant the team-screenshot permission. It opens on today with a folder per employee, and any day can also be read as a day view, a grid, a list or a folder tree, filtered by person. Opening a frame shows it full size with zoom, the date and time, the person, what was shared — screen, window or tab — and, when there is one, the project and task they were working on. Deleting a frame is a separate permission again.

A count of screenshots cannot tell someone who is not working from someone whose browser never started sharing. So Team Screenshots opens with a Not being captured panel: everyone who is checked in right now but producing no screenshots, each with the reason in plain words.

• Declined the screen-share prompt
• Stopped sharing, or closed the tab
• Screen capture failed to start
• Never started — checked in without sharing their screen

Each row also says how long it has been that way, how many screenshots the person has today and when the last one was taken. The panel refreshes live while the page is open and disappears when there is nothing to fix. It is there to tell you who to ask, not who to blame — a declined prompt is usually a missed click on a busy morning.

Capture runs in the browser, so there is nothing to install and nothing to roll out to laptops. The trade-off is that the browser sets the rules: one share covers one screen, one window or one tab, and closing the tab ends the share — which the capture-health panel then reports. A desktop app for attendance and capture is planned and marked coming soon, with no date. Everything on this page describes what the browser does today.

Screenshots are one part of AMS, next to clock-in, timesheets and leave. If what you need is a record of hours rather than pictures of screens, the idle policy and timesheets may be enough on their own; screen capture is a switch you can leave off.