Desktop tracker
Installation on each operating system, what happens when the network drops, how updates reach a fleet, and the three things that usually go wrong.
Supported platforms
| Platform | Versions | Screen capture | Install notes |
|---|---|---|---|
| Windows | 10 and 11, 64-bit | Yes | Signed installer, per-user install, no administrator rights required |
| macOS | 11 Big Sur and later | Yes | Notarised. The user grants Screen Recording permission once, in System Settings |
| Ubuntu / Linux | 20.04 LTS and later | Xorg only | Wayland sessions cannot be captured. Time and activity still record |
Check the session type before a Linux rollout. Run echo $XDG_SESSION_TYPE. If it returns wayland, screenshots will not capture; either switch the login session to Xorg or run those machines with screenshots disabled.
Installation
- Download the build for the platformFrom the Desktop App page inside the portal, so the download is already tied to your installation.
- Install and sign inThe same email and password the employee uses for the web portal. On a self-hosted installation the server URL is set at first run.
- Grant the screen permissionmacOS only, and only if screenshots are enabled. The app cannot capture until the user grants it, by design.
- Start trackingThe tray icon appears and stays visible for as long as recording is active.
Offline queue
The application does not depend on connectivity to record.
- Sessions, activity intervals and screenshots are written to a local queue first, always.
- Upload happens in the background, in order, whenever the server is reachable.
- The queue survives application restarts and machine reboots.
- Uploads are idempotent, so a partial upload retried after a drop does not duplicate a session.
Automatic updates
The app checks an update feed on start and periodically thereafter, downloads a new build in the background and applies it on the next restart. On cloud installations the feed is ours; on a self-hosted installation it points at your own server, so a fleet updates when you publish a build.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Screenshots are blank or missing on Linux | Wayland session | Switch to an Xorg session, or disable screenshots for those machines |
| Screenshots blank on macOS | Screen Recording permission not granted | System Settings, Privacy and Security, Screen Recording, then restart the app |
| Time not appearing in the portal | Queued offline, or the server URL is wrong | Check the tray status; on self-hosted confirm the configured server URL resolves |
| Activity always shows zero | Accessibility permission missing on macOS | Grant Accessibility permission and restart the tracker |
| App does not start on Windows | Blocked by endpoint protection | Allow the signed publisher in your endpoint policy |
Related
Frequently asked
Does the tracker work offline?
Yes. It records normally without a connection, queues sessions, activity data and screenshots on the local disk, and uploads the backlog in order when connectivity returns. The queue survives a restart of the application and of the machine.
How large can the offline queue get?
It is bounded by local disk. Several days of queued screenshots is normal and supported; the app warns when the queue is unusually large so a permanently broken connection gets noticed.
Can we deploy it silently across a fleet?
The Windows installer supports a silent switch for deployment through your existing management tooling. The application itself is never silent to the user once installed.
Something missing from the docs?
Tell us what you were looking for at support@employeedeskcrm.com and we will add it here.
- 7-day trial
- No credit card
- Cancel anytime