¶ 2. Dashboard
Application: Portal Nomid MDM
Document: V1.1.0
Last updated: 02/07/2026
Editorial owner: Nomid MDM Documentation
Last editorial review: 02/07/2026
Editorial language: en-US
The Dashboard brings together executive and operational indicators of the managed fleet. It helps you quickly identify usage deviations, sync failures, geographic concentrations, data consumption, and adoption trends.
Important: The numbers depend on the last report sent by the devices. Equipment without recent synchronization may leave graphs and counters incomplete.
¶ Overview
¶ Dashboard Summary
The top of the Dashboard combines current fleet status counters with a period selector for trends and historical metrics.
Use this area to see how many devices are active, syncing, external, or deleted and to choose the chart analysis window. The selected period does not turn current status counters into historical totals.
¶ Screen elements
- 7D, 30D, and 90D: change the window used by trends and historical metrics to the last 7, 30, or 90 days.
- All: uses the longest history made available by the portal for that indicator; it does not mean unlimited retention.
- Calendar: defines a custom range when you need to correlate data with a rollout or incident.
- Active devices: counts devices whose current status is Active.
- Syncing devices: counts devices being provisioned or synchronized. This is an intermediate state and is not proof that the policy has been applied.
- External Devices: counts records classified as external; this status is not proof that the device is managed by Android Enterprise.
- Deleted devices: counts deleted records retained in Dashboard history; they are not part of the active fleet.
¶ Data refresh and reliability
- The Dashboard queries independent datasets for fleet, usage, map, and security. One card may be current while another is still loading, has failed, or contains older information.
- While the page is visible, the portal attempts to refresh data about every 60 seconds and again when you return to the tab. This does not force a new device report.
- The Dashboard update time indicates when the portal received the query response. To assess the actual age of device data, check Last sync, the collection time, or the corresponding report in Devices.
- When a card reports an error, use that card's retry action. If the value still differs from expectations, open the details and compare status, policy, and last sync for the affected devices.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Choose the analysis period, read the cards and prioritize investigation when there is an increase in alerts, a drop in online or an accumulation of pending issues. Use these numbers as a starting point for filtering devices in the Devices module.
¶ Device registrations
¶ Device registrations screen
The graph of device enrollments/enrollments in the selected period.
This area is used to validate whether new devices are being registered at the expected rate and whether a mass deployment via QR Code, Zero-touch or KME actually generated new registrations.
¶ Screen elements
- Registration graph: shows the evolution of new device registrations in the selected period.
- Enrollment spikes: help validate provisioning waves via QR Code, Zero-touch or KME.
- Dropped or missing records: indicates a need to review the token, connectivity, Android Enterprise link or activation process.
- Comparison by date: relates planned deployments to records actually created in the portal.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Adjust the Dashboard period and compare the graph peaks with the provisioning dates. If the graph does not grow after a deployment, review enrollment token, connectivity, Android Enterprise bonding, and provisioning policies.
¶ Map
¶ Dashboard Map
The map with the last known location of devices that reported geolocation.
This area is used to visualize the geographic distribution of the fleet, identify concentration by region and investigate equipment outside the expected area.
¶ Screen elements
- Geographic map: displays the distribution of devices with reported location.
- Point groupings: indicate concentration of equipment by region, branch or area of operation.
- Zoom and drag: allow you to analyze specific regions with greater precision.
- Devices outside the expected area: help identify improper displacement, loss, theft or allocation error.
- Absence on map: generally indicates disabled location, offline device or lack of permission/connectivity.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Use zoom, drag the map and click on points or groupings to analyze regions. If a device does not appear, verify that location collection is enabled in the policy, that the device is online, and that there is permission/connectivity to report location.
¶ Fleet overview
¶ Fleet overview screen
The Fleet overview card, with an operational summary of the fleet.
This area is used to quickly compare fleet states, such as active, offline, alerted, pending or out of compliance, according to the indicators available in the company.
¶ Screen elements
- Fleet States: groups devices by operational condition, such as active, offline, pending, or alerted.
- Comparative indicators: quickly show where there is a greater concentration of risk or outstanding issues.
- Daily Reading: supports the screening routine before opening the full device list.
- Opening by filter: allows you to transform an indicator into an investigation in the Devices module.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Use the card as a daily check. When you notice abnormal volume in any state, open Devices, apply equivalent filters and treat the affected devices by group, policy or last sync.
¶ Devices by group
¶ Devices by group screen
The card that distributes devices by group.
This area is used to understand how the fleet is segmented by customer, branch, project, contract or operational group. Helps you find empty, overcrowded, or misallocated groups.
¶ Screen elements
- Operational groups: represent customer, branch, contract, project, class, team or any segmentation defined by the company.
- Fleet distribution: shows whether the devices are allocated according to the planned structure.
- Empty or overcrowded groups: signal incomplete registration, incorrect movement or need for inventory review.
- Allocation adjustment: must be made in the device file or by movement action when there is a discrepancy.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Compare the displayed groups with the expected organization structure. If there is a discrepancy, open the device or use allocation actions to adjust group, owner, or related policy.
¶ Screen time
¶ Screen time screen
The fleet aggregate screen time graph.
This area is used to monitor the intensity of use of devices and detect patterns such as excessive use, low use, working hours that are not expected or equipment that is stopped.
¶ Screen elements
- Usage metric: indicates how long devices spent on screen during the selected period.
- Journey pattern: helps detect after-hours usage, idle equipment, or excessive usage.
- Comparison by date: shows variations in behavior throughout the operation.
- Investigation by device: must be in-depth in the Usage tab of the equipment sheet.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Analyze the period, compare days and identify groups with unusual behavior. To investigate a specific device, open the file in Devices > Usage and compare screen time with app usage and connectivity.
¶ Safety and operational attention
¶ Security
The fleet safety indicator card.
This area is used to view situations such as non-compliant devices, problematic security posture, pending configurations, or events that require administrator action.
¶ Screen elements
- Compliance indicators: summarize devices at risk, pending configuration, or inadequate security posture.
- Critical events: must be handled before low priority adjustments.
- Relationship with policies: allows you to identify whether password, FRP, restrictions, Play Integrity or blocks are applied correctly.
- Latest Report: helps differentiate active problem from old information sent by the device.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Review indicators and address critical items first. Then go to the applied policy and device profile to check password, FRP, Play Integrity, restrictions and last status report.
¶ Data consumption
¶ Data consumption screen
The graph of mobile data/network consumption in the period.
This area is used to identify high consumption, non-standard peaks and possible misuse or apps consuming more data than expected.
¶ Screen elements
- Tracked volume: shows data consumption in the selected period.
- Traffic spikes: signal heavy sync, out-of-scope application, or misuse.
- Relationship with apps: must be compared with the data ranking per application.
- Control by Policy: May restrict applications, tethering, networking, or behavior incompatible with the device's function.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Adjust the period and compare consumption with usage events. To investigate, open the breakdown by app in the Dashboard or the device's Usage tab. Use policy to restrict apps, networking, tethering, or behavior outside of the device's function.
¶ Most used apps by time
¶ Most used apps by time screen
The ranking of most used applications by time.
This area is used to find out which apps concentrate the most usage time in the fleet and confirm whether usage is aligned with the corporate purpose of the devices.
¶ Screen elements
- Application ranking: ranks the apps that have the most usage time.
- Time per app: confirms whether the device's routine adheres to the corporate objective.
- Unwanted apps: indicate the need to review the allowlist, kiosk, launcher and installation rules.
- Analysis prioritization: directs investigation to the applications that most impact productivity.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Notice the apps at the top of the list. If inappropriate apps appear, review the application policy, kiosk/launcher mode, Play Store allowlist and installation rules.
¶ Most used apps for data
¶ Most used apps for data screen
The ranking of applications with the highest data consumption.
This area is used to discover which apps most impact mobile franchise, connectivity and operational costs.
¶ Screen elements
- Traffic ranking: identifies which applications consume the most mobile or Wi-Fi allowance.
- Operational Impact: Helps reduce data cost and find excessive syncs.
- Heavy applications: must be reviewed in permissions, managed configuration and update policy.
- Corrective Action: may involve removing, restricting, blocking, or adjusting app settings.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Use the ranking to prioritize analysis of heavy apps. If necessary, adjust app policy, set restrictions, remove non-essential apps, or investigate whether your corporate app is syncing too much data.
¶ Application versions
¶ Application versions screen
The application version card installed in the fleet.
This area is used to check version dispersion and identify devices that have not yet updated a critical app.
¶ Screen elements
- Distribution by version: shows which versions of an application are present in the fleet.
- Lag: identifies devices that have not yet updated the expected app.
- Standardization: supports auditing to maintain all equipment in the approved version.
- Correction: must be done via app policy, library, or device connectivity check.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Compare the expected version with the listed versions. When there are older versions, review the automatic update policy, availability on Managed Google Play, connectivity and installation status on the device listing.
¶ Hidden Cards
¶ Hidden Cards screen
The hidden cards or card customization area of the Dashboard.
This area is used to control which indicators appear in the main view, reducing noise and leaving the most important cards for the operation visible.
¶ Screen elements
- Available Cards: list indicators that can be shown or hidden on the Dashboard.
- Vision customization: allows you to highlight only metrics relevant to the operation.
- Hide indicator: reduces visual noise when a metric is not used by the team.
- Redisplay indicator: brings back cards needed in audits, support or temporary monitoring.
¶ How to use the indicator
- Use the card as an entry point: adjust the period, read trend and volume, then open Devices when you need to investigate specific devices.
- Compare the indicator with groups, policies, and last sync to separate a real problem from collection delay.
- When there is a spike, drop, or missing data, confirm that the corresponding collection is enabled in the applied policy.
¶ Application in operation
- Access the card configuration, select or deselect the desired indicators and save the visualization. Use this to create a leaner Dashboard for support, operations, security or management.