Device activity & analytics
Device activity monitoring that starts only after consent is approved
See when each company computer is in use, idle, locked, asleep or offline, who is signed in and how hard it is working — with timelines, Top 10 lists and exports, behind a signed authorisation that Infronest approves first.
How much does Device Activity cost?
₹49 per user per month, on endpoints that run MDM Enterprise or Patch Management. The full activity timeline needs the MDM agent. Device Activity is also part of the Security Starter Bundle with EDR and DLP Basic. See Device Activity pricing.
Already live in the product
Live in the product today: the Device Activity overview, Top 10 lists, user and device timelines, alert rules, CSV, XLSX and PDF reports, and the consent workflow that keeps collection off until it is approved.
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
- Sign-in, sign-out, lock, idle, sleep, shutdown and restart events
- Online and offline presence worked out every two minutes
- CPU, RAM and disk use, with time spent above your CPU and RAM thresholds
- Top 10 lists for idle time, uptime, offline time and restarts
- Daily usage per device and per user, with the assigned user
- Ten report types in CSV, XLSX and PDF, audited on export
- In-app alerts for resource use, uptime, offline time and restarts
- Signed authorisation and Infronest approval before collection starts
What teams can do here
- Step 1Switch on Device Activity for your organisation
- Step 2Acknowledge the monitoring notice
- Step 3Sign, stamp and upload the authorisation PDF
- Step 4Turn collection on once Infronest approves
- Step 5Review timelines, Top 10 lists and reports
How it works
- 01
Read and acknowledge the notice
An admin with the Device Activity manage permission opens Settings and reads the monitoring notice: what is recorded, what is never recorded and how long it is kept. The admin then acknowledges the current version, and a copy of the notice text is stored with that acknowledgement.
- 02
Sign the authorisation
Download the Company Device Monitoring & Authorisation Notice as a PDF, already filled in with your company details. An authorised signatory signs it and adds the company seal.
- 03
Upload it for approval
Upload the signed copy as a PDF, PNG or JPEG of up to 15 MB. Infronest is notified and reviews it. We either approve the activation or reject it with a reason, and you can upload a corrected copy.
- 04
Switch collection on
Once approved, the admin turns collection on and sets the idle threshold (1–60 minutes, 5 by default), the time zone, alert thresholds and how long raw events are kept (30–90 days). Agents pick up the change at their next configuration check.
- 05
Read the activity
Timelines, daily usage and Top 10 lists fill in as events arrive. Reports export with the assigned user’s name and email on every device row.
A worked example
Say a 300-person logistics company in Pune wants to find out which laptops are barely used before it renews 40 leases. The IT admin switches on Device Activity, acknowledges the notice and downloads the authorisation PDF. The HR head tells staff that activity on company laptops will be recorded, then signs and stamps the form, and the admin uploads the scan. Once Infronest approves, collection starts with a 10-minute idle threshold. A month later, the most-idle Top 10 list and the monthly-usage export point to 23 laptops that were signed in for under an hour a day, each listed with its assigned user’s name and email. IT checks with the managers and reassigns 15 of them instead of renewing the leases. Every report download is on the audit trail.
How the consent gate works
Activity monitoring touches personal data, so Device Activity records nothing until five conditions hold, in this order. The module is switched on for your organisation. Infronest MDM is active for it. An admin has acknowledged the current notice. Infronest has reviewed and approved the activation. Finally, the admin turns collection on.
Until then, agents are told not to collect and discard anything they had buffered, the server stores no activity events, and nothing dated before the approval is ever written. If a check cannot be completed, the answer defaults to “do not collect”. If the notice is updated, collection locks again until the new version has been acknowledged and approved.
The gate covers Device Activity’s own recording. Health signals your MDM agent already reports, such as online status, restarts and CPU, RAM and disk use, stay visible as before.
What is recorded, and what never is
Device Activity records state changes, not content. It logs sign-ins and sign-outs, lock and unlock, idle start and end, sleep and wake, shutdowns, restarts and boots, plus online and offline presence that the server works out every two minutes. On Windows it also notes whether a user, the system or an update started a restart. It records that category only, never the comment text.
It never records keystrokes, screenshots, window titles, process names, websites or URLs, or what is inside files, email or chats. These limits describe Device Activity; modules such as remote access or DLP have their own scope, set out on their own pages.
Coverage by operating system
What a device reports depends on the agent it runs. CPU, RAM and disk use come from the MDM agent’s regular check-ins, and five-minute samples are kept for 30 days.
Reports, Top 10 lists and alerts
The overview counts devices that are online, offline, active, idle, sleeping or locked, and flags high CPU or RAM, long uptime and machines that have not restarted. Seven Top 10 lists rank devices by days without a restart, CPU, RAM, uptime, offline time, idle time and number of restarts. Each row opens the device, and the assigned user’s name opens that person’s activity.
Ten export reports cover daily user and device activity, device health, restarts, offline time, high CPU, high RAM, sleep and shutdown, monthly usage and the Top 10. They export as CSV, XLSX or PDF for ranges of up to 366 days. Device rows carry the assigned user’s name and email, and every export and drill-down view is written to the audit log.
Alert rules watch CPU, RAM and disk use, uptime, days without a restart, hours offline and frequent restarts, and each rule can be limited to a device group or operating system. Rules are checked every five minutes, and alerts resolve themselves when the condition clears. Alerts appear in the app; this module sends no alert emails or scheduled reports today.
Pricing and what you need first
Device Activity is ₹49 per user per month. Each endpoint needs MDM Enterprise (₹850 per endpoint per month, minimum 50 endpoints) or Patch Management, and the full activity timeline needs the MDM agent. Device Activity also comes in the Security Starter Bundle with EDR and DLP Basic at ₹299 per user per month. See the bundles on the pricing page.
Devices enrolled before the module was switched on need an agent update before they report sessions, lock and idle. Newly enrolled devices get the collector from the start.
Frequently asked questions
See also: MDM software · Patch management · DPDP compliance operations · Data loss prevention · Device Activity pricing
Know how company devices are used, with the paperwork done first
Sessions, idle time, restarts and resource use per device and user, behind a signed authorisation and Infronest approval. Walk through the consent flow with us.
