What problems it solves
Without reports, a fleet is a list of serial numbers. IT teams need to plan Android upgrades, find devices that are about to fail, justify the budget and spot devices that sit unused in a drawer.
- Visibility: one dashboard for the whole fleet.
- History: every device keeps its own timeline of versions, users, states and policies.
- Evidence: reports export to Excel for audits and budget planning.
The dashboard
The home page of the console answers the first questions of the day. It shows how many devices are enrolled, active and online right now, how many users there are, and how devices split by state and by management mode. A map tab shows the last known location of devices, and a connection chart shows how many devices connected on each of the last seven days.
The device detail
Every device page brings together:
- hardware and identity (manufacturer, model, serial, IMEI, device certificate),
- Android version history and DeepManage agent version history, with the management mode (fully managed or work profile),
- battery, storage, CPU and memory history,
- network usage history split into total and mobile data,
- SIM card and phone number history,
- the policies in force, policy results and errors, and policy history,
- state changes (active, in service, lost or stolen) and user history,
- installed apps and location history.
Fleet reports
| Group | Reports |
|---|---|
| Versions | Android version distribution, DeepManage version distribution |
| Structure | Distribution by state, role, profile, device group, division and department |
| Gaps | Devices without an organization or device group, unused devices, users who have not connected |
| Apps | Top 10 installed apps, app reports with install counts and most used hours |
| Resources | Devices with nearly full storage, mobile data report, GSM and SIM reports |
| Growth | Devices activated by month |
Push messages sent through the API have their own report, described on the messaging page. Policy results for each device are explained on the policies page.
Personal data and KVKK
Some records describe a person, not only a device: location, call history and network logs (DNS lookups and connections). DeepManage collects call history, security logs and network logs only when a policy turns them on, so you can limit them to the devices where you have a reason. Set short retention periods, restrict who can view these reports with roles and permissions, and inform employees before you start. Our KVKK and GDPR guide covers the basics. This is general information, not legal advice.