¶ 3. Devices
Application: Portal Nomid MDM
Document: V1.1.2
Last updated: 10/07/2026
Editorial owner: Nomid MDM Documentation
Last editorial review: 10/07/2026
Editorial language: en-US
The Devices module concentrates the daily operation of the fleet: inventory, filters, map, technical data sheet, usage, applications, applied policy, location and remote commands.
Important: Some of the actions depend on the device being online and communicating again with Android Device Policy or the management agent.
¶ List and map
The Devices module is available in the side menu and centralizes the operational fleet view, with access to the list, map, and individual device record.
¶ Toggle list or map
¶ Result of selections and settings
- List: prioritizes inventory, filters, columns, bulk actions, and tabular comparison.
- Map: prioritizes geographic distribution, regional concentration, and location investigation.
- Switch to list: helps operate many devices with filters and multi-select.
- Switch to map: helps identify assets outside the expected area.
- Device missing from map: usually means no location, disabled collection, or offline device.
The selector that switches the view between List and Map on the devices screen.
This area is used to choose between a tabular view for detailed operation and a geographic view for location analysis.
¶ Screen elements
- List button: displays devices in a table for inventory analysis, status and bulk actions.
- Map Button: Displays devices by last known location.
- Choice criteria: use list for administrative operation and map for geographic analysis.
- Preserved state: The chosen view helps maintain the operator's workflow.
¶ Application in operation
- Select from List to work with columns, filters and bulk actions. Click Map to view device locations. Use the list when you need to act; Use the map when you need to understand distribution or displacement.
¶ Device list
The master list of devices with identification, status, and operational attribute columns.
This area is used to query inventory, compare devices, check policy, group, model, IMEI, last sync and select items for individual or mass actions.
¶ Screen elements
- Device lines: represent each device registered in the company.
- Inventory columns: display identification, status, policy, group, user, model and last communication depending on availability.
- Item Selection: Enables bulk actions for groups of devices.
- Access to the card: the device name, identifier or card opens the full details.
¶ Application in operation
- Use search, filters and columns to reduce the list. Click on the device name to open the tab. Select checkboxes when you want to perform actions on multiple devices.
¶ Device map
Viewing devices on a map, with a side list and geographic points.
This area is used to locate equipment in the territory, cross status with position and identify devices outside the expected area.
¶ Screen elements
- Markers: indicate the last location reported by devices.
- Group: summarizes multiple nearby devices for easier reading in large fleets.
- Zoom: zooms in on regions, branches, routes or risk areas.
- Device without position: may be offline, not collecting location, or without valid permission/report.
¶ Application in operation
- Switch to Map, navigate the map and click on the points or devices in the side list. For missing devices, check location collection, permissions, and last sync.
¶ Search
¶ Device search
The device list search field, including the AI-assisted search option when available.
This area is used to find devices by name, IMEI, series, model, policy, group, status or operational description.
¶ Screen elements
- Search field: locates devices by name, IMEI, serial number, user, group or term available in the inventory.
- Filtered result: reduces the list to equipment compatible with the term entered.
- Operational search: accelerates service when support receives IMEI, assets or user identification.
- Combination with filters: refines analysis by status, group, policy or condition.
¶ Application in operation
- Type the term in the field and press Enter. For assisted searches, describe the intent, for example “Samsung devices not synced in more than 7 days,” and review the filters you applied before taking action.
¶ Filters
¶ Filters screen
¶ Result of selections and settings
- Status/connectivity filter: separates online, offline, pending, or alert devices to prioritize support.
- Group/policy filter: restricts the list to an operation, customer, or rule set.
- Model/system filter: helps actions by manufacturer, Android, or compatibility.
- User/allocation filter: locates owners, stock, maintenance, or loan devices.
- Combining filters: reduces noise but can hide devices if criteria are too restrictive.
- Clear filters: returns to the full fleet view.
The device listing filter pane.
This area is used to refine the fleet by identifiers, installed applications, policy, group, status, last sync date and other available fields.
¶ Screen elements
- Status: separates online, offline, pending, alerted or non-compliant devices according to the available filters.
- Group: limits the list to a branch, customer, project or operating segment.
- Policy: only shows devices associated with a specific rule.
- Model or System: Helps investigate issues focused on manufacturer, Android version, or device type.
- Clear filters: returns to the full view after analysis.
¶ Application in operation
- Select Filters, choose the filter, enter the value and apply. Combine filters to find specific cases, such as “devices in a policy that haven’t synced since yesterday.”
¶ Columns
¶ Columns screen
¶ Result of selections and settings
- Show column: adds the data to the list and helps comparison without opening the record.
- Hide column: simplifies the view and reduces visual noise.
- Identification columns: help avoid acting on the wrong device.
- Status/sync columns: help prioritize support and confirm communication.
- Policy/group columns: support audit and bulk actions.
- Save view: reuses the combination in future routines when available.
The visible columns menu of the device list.
This area is used to customize what information appears in the table, facilitating audits and exports according to the service objective.
¶ Screen elements
- Column selector: defines which information appears in the table.
- Identification columns: include name, IMEI, serial, model and user when available.
- Operational columns: include status, policy, group, last sync, battery, network and alerts depending on the company.
- Routine customization: allows you to create a leaner view for support, inventory or auditing.
¶ Application in operation
- Select Columns, enable or disable fields, and rearrange the view as needed. For support analysis, prioritize status, last sync, policy, model, IMEI and relevant apps.
¶ Saved Views
¶ Saved Views screen
¶ Result of selections and settings
- Save view: stores filters, columns, sorting, and display mode for recurring use by the current user and company.
- Apply view: quickly restores a working view such as offline, stock, or support.
- Update view: replaces the saved configuration with the current view without recreating it.
- Set as default: makes the view open automatically as that operator's starting point.
- Delete view: removes a local view that should no longer be used.
The devices screen saved views menu.
This area is used to save filter, column, and view combinations for reuse in operation routines.
¶ Screen elements
- View: saves combination of filters, columns, ordering, and display mode for reuse.
- Support view: can prioritize status, last sync and diagnostic actions.
- Inventory view: can prioritize IMEI, serial, model, user and group.
- Per-operator persistence: the view is tied to the user, company, and browser used, without indicating sharing with other operators.
¶ Application in operation
- Configure filters and columns, open Views and choose Save current view. Use Set as default when you want the same view to return as the starting point. If another operator needs the same reading, they must save an equivalent view in their own access.
¶ Device card
¶ Device card screen
The summary card of a device, with identification, status and location/main attributes.
This area is used to quickly check the status of a device without opening the entire file, including data such as model, IMEI, policy, security status and last known location.
¶ Screen elements
- Main identification: shows name, model, IMEI, serial number or other identifier used to recognize the equipment.
- Communication status: indicates whether the device is online, offline, or recently synced.
- Policy and group: show the administrative context applied to the equipment.
- Quick indicators: summarize battery, network, user, alerts or important data depending on availability.
- Access to detail: opens the complete form for diagnosis and remote actions.
¶ Application in operation
- Click the device in the list or map to open the card. Use the summary to confirm that it is the correct equipment and then open the full file or perform a contextual action.
¶ Actions by device in the list
¶ Device actions in the list
¶ Result of selections and settings
- Open Device: opens the record to validate data before acting.
- Remote Access: starts remote assistance when the feature is enabled for the company and the device supports it.
- Change Policy: changes the applied policy and may alter apps, restrictions, network, launcher, and collection.
- Force Status Report: requests a new report to update status, apps, policy, network, and inventory.
- Reboot/Power: restarts the device, temporarily interrupting use.
- Lock: locks the screen for containment or support.
- Change Password: changes the local password when the model and management type allow it.
- Launch App: opens an application on the device for support or assisted operation.
- Lock App Kiosk: puts the device in focus/kiosk on the chosen app when applicable.
- Start/Stop Lost Mode: starts or ends lost mode for loss, theft, or recovery scenarios.
- Usage Report: requests a usage report for operational analysis.
- Clear Apps Data: clears data from selected apps; it may sign users out and remove local app data.
- Wipe Data: erases device data or the managed area, depending on management type.
- Relinquish Ownership: removes corporate ownership from a compatible device while keeping personal use when allowed.
The actions menu for a device in the listing.
This area is used to open the device page, change policy, or run sensitive remote commands depending on permissions, connectivity, and model support.
¶ Screen elements
- Action menu: brings together commands available for the selected device.
- Open details: leads to the technical and operational data sheet of the equipment.
- Change policy: changes the administrative framework of the asset when authorized.
- Remote commands: perform actions such as request report, lock, restart, change password, launch app, start lost mode, clear app data, or erase data depending on device permissions and support.
- Destructive actions: must be confirmed carefully as they affect data or availability.
¶ What each command allows
- Open Device: opens the device record for analysis before any action.
- Change Policy: moves the device to another policy and can change apps, restrictions, and collection.
- Force Status Report: requests a state update to confirm policy, apps, network, and recent data.
- Lock/Reboot/Change Password: supports service and containment, but depends on connectivity and model support.
- Launch App/Lock App Kiosk: forces opening or focus on an app for guided assistance or dedicated operation.
- Lost Mode: helps protect and recover lost equipment when supported.
- Clear Apps Data: clears local data from selected apps; use carefully with apps that have unsynced data.
- Wipe Data/Relinquish Ownership: are high-impact actions; use only after validating asset, IMEI/serial, authorization, and operational consequence.
¶ Checklist for destructive actions
Before confirming Wipe Data, Relinquish Ownership, or Clear Apps Data, validate:
- Management type: on a fully managed corporate device, wipe may factory reset the device; on a personal device with a Work profile, the action may affect only the managed area.
- Relinquish Ownership: use only when the model supports relinquishing corporate ownership. The goal is to remove corporate management and preserve allowed personal use; after that, the device must be enrolled again to return to management.
- Offline device: the command may remain pending or return a partial result until the device connects and acknowledges the action.
- Evidence and recovery: record authorization, IMEI/serial, user, reason, and the re-enrollment or return plan before execution.
¶ Application in operation
- Access the Actions menu for the correct device. Choose the desired action and confirm only after reviewing the name, IMEI and impact. Destructive actions must only be used with authorization.
¶ Bulk Actions
¶ Bulk Actions screen
¶ Result of selections and settings
- Apply bulk action: runs the command on the selected scope, which may be only the current page or all filtered devices.
- Select current page: limits the action to visible/selected items on the page.
- Select all filtered: expands the action to all devices matching the current filters, even when they are not visible.
- Bulk policy/group change: standardizes quickly but can affect apps, restrictions, and connectivity.
- Bulk sync/report: useful after publishing a policy to speed up state updates.
- Bulk lock/reboot: requires an operational window to avoid interrupting users.
- Bulk Launch App/Lock App Kiosk: opens or pins an app on several devices, respecting portal limits and support.
- Bulk Usage Report/Clear Apps Data: collects usage or clears app data in batches; offline devices may produce partial results.
- Bulk Wipe/Relinquish Ownership: critical action; validate filters, count, and authorization before confirming.
- Partial result: some devices may fail because they are offline or do not support the command.
For destructive bulk actions, treat Select all filtered as the real operation scope, even when some devices are not visible on the page. Before confirming, export or record the filtered count, apply first to a pilot batch, and monitor pending/offline results until the operational window is closed.
The bulk actions menu after selecting devices.
This area is used to apply commands to several devices, such as changing policy, requesting report, restarting, locking, changing password, launching app, locking app in kiosk, generating usage report, clearing app data, wiping data, or relinquishing ownership according to company availability.
¶ Screen elements
- Multiple Selection: allows you to select multiple devices before performing an action.
- Page/all filtered scope: defines whether the command will affect only the page selection or all filter results.
- Batch application: reduces operation time when changing policy, group or administrative commands.
- Selected scope: must be reviewed before commit to avoid impact on wrong devices.
- After-action monitoring: must be done through the status, last sync and history of affected devices.
¶ What each command allows
- Manage selected: applies an action to selected devices and should be used only after reviewing count and filters.
- Change policy/group in bulk: standardizes large groups, but can change experience, apps, and restrictions for many users.
- Sync/Report in bulk: forces an operational update without changing data, useful after publishing a policy.
- Sensitive commands: lock, reboot, remove, or wipe require an operational window and authorization.
- Follow-up: track execution in history and last sync to identify individual failures.
¶ Application in operation
- Mark the devices in the list, click Manage selected and choose the action. Before confirming, validate the selected quantity and use filters to avoid applying commands to the wrong devices.
¶ General actions
¶ General actions screen
General actions on the Devices screen, such as exporting, importing and registering a new device.
This area is used to create new records/enrollments, batch import devices, or export the current listing for external analysis.
¶ Screen elements
- Add devices: starts the enrollment flow or registration of new equipment.
- Export: generates a file for inventory, auditing or cross-referencing with other systems.
- Update list: forces reloading of data displayed on the portal.
- View Settings: adjust columns, filters and display mode.
¶ What each option allows
- New device/Add devices: starts registration, enrollment, or resource generation for new equipment.
- Import devices: allows bulk loading when the operation already has a spreadsheet or external inventory.
- Export as .xlsx: generates an auditable view of the filtered list for inventory and reconciliation.
- Refresh: reloads the screen to validate recent changes.
- Columns/filters/views: adjust visualization without changing devices.
¶ Application in operation
- Use New device to start registration/provisioning, Import Devices for batch loading and Export as .xlsx to generate a spreadsheet with filtered/visible devices.
¶ Device sheet — Summary
¶ Device Summary
The Summary tab is the starting view of the device record and organizes access to the other operational tabs, such as usage, history, policy, system, apps, location, and allocation.
The summary tab of the individual device file.
This area is used to consolidate device identification, status, policy, main apps, location, network, security, and quick information on a single screen.
¶ Screen elements
- Asset identification: brings together name, model, IMEI, serial number, user and other central data.
- Current State: Shows connectivity, battery, policy, group and relevant alerts.
- Last communication: indicates when the portal received recent information from the device.
- Detail tabs: organize usage, policy, system, apps, location and allocation.
¶ Application in operation
- Access the device from the list and read the summary before executing any commands. Use the links, cards and side tabs to delve deeper into usage, system, apps, location and allocation.
¶ Individual actions on the sheet
¶ Individual shares
The individual actions menu available within the device tab.
This area is used to execute remote commands on the specific device, such as request report, restart, lock screen, change password, change policy, launch app, lock app in kiosk, start/stop lost mode, clear app data, wipe data, or relinquish ownership when the device supports it.
¶ Screen elements
- Actions: opens specific commands for the device under analysis.
- Force Status Report: requests status update and policy application when available.
- Lock/Reboot/Change Password: supports operational support and containment.
- Change Policy: adjusts the applied policy according to permissions.
- Launch App/Lock App Kiosk: opens or pins an app for assisted support or dedicated use.
- Lost Mode: protects the device in case of loss or theft when supported.
- Clear Apps Data/Wipe/Relinquish Ownership: should be reserved for incidents, disposal, recovery, or authorized maintenance.
¶ What each command allows
- Manage device/Actions: runs commands only on the device opened in the record.
- Request report/Sync: updates data to validate state, policy, and collection before corrective action.
- Change Policy: changes the applied policy and can modify rules, apps, and restrictions.
- Remote Access/Launch App/Lock App Kiosk: supports user assistance when the device is reachable.
- Lost Mode: helps contain and recover a lost device when supported.
- Clear Apps Data/Wipe Data/Relinquish Ownership: are high-impact actions and should be recorded according to the internal process.
For commands that collect or expose device data, use only the approved purpose for support, security, or operation. Usage reports, location, IMEI, serial, network data, and logs must be shared only through authorized corporate channels and kept only as long as needed for the case.
¶ Application in operation
- Access Manage device or Actions, select the command and confirm. For network-dependent commands, monitor the status and request a new report if you need to validate the application.
¶ Device usage
¶ Device usage screen
The Usage tab concentrates device utilization indicators and serves as the entry point for deeper analysis by period and by application.
The device usage tab with aggregated indicators and graphs.
This area is used to analyze screen time, data consumption, energy and general behavior of the equipment over the period.
¶ Screen elements
- Usage timeline: summarizes equipment activity in the analyzed period.
- Screen time: shows intensity of use and adherence to the expected journey.
- Data consumption: indicates impact on franchise and connectivity.
- Usage Events: help you investigate what happened before a crash or alert.
¶ Application in operation
- Choose the desired period and read the charts. Use usage spikes as a trigger to investigate apps, user, location, or need for policy adjustment.
¶ Usage by application
¶ Usage by application screen
The usage list per application within the device sheet.
This area is used to identify which apps consume the most time, data or battery on a specific device.
¶ Screen elements
- App list: shows the applications that have registered use on the device.
- Time per application: indicates which apps concentrate user activity.
- Data by application: shows the impact of each app on connectivity.
- Policy Comparison: helps confirm whether the app used is allowed and expected for the device's function.
¶ Application in operation
- Sort or filter the list by available indicators. When you find an inappropriate app or app with abnormal consumption, review installation, permissions, managed configuration, and policy rules.
¶ App Usage Detail
¶ App Usage Detail screen
The usage breakdown for an individual application.
This area is used to see app behavior over time, such as foreground usage, data consumption and variations by period.
¶ Screen elements
- Selected application: identifies the individually analyzed package.
- Detailed Metrics: Shows time, data, events, or app-specific behavior.
- Consumption Diagnosis: Helps you find excessive synchronization, misuse or configuration error.
- Policy adjustment: may involve removing, blocking, allowing, or managed configuration of the app.
¶ Application in operation
- Select an app in the usage list to open the detail. Compare usage with expected hours of operation and take policy action if the app is outside of the device's intended purpose.
¶ Connectivity and operational events
¶ Connectivity and events
The History tab organizes the operational history of the device and brings together commands, responses, remote executions, and filters for event- and period-based review.
The device's connectivity/events tab, with history of changes and reported signals.
The command filter lets you narrow the view to specific event types, such as remote access, remote password, or reboot actions.
¶ Result of selections and settings
- Command filter: shows only events of the chosen type, such as sync, reboot, password, or wipe.
- Short period filter: speeds investigation of a recent incident.
- Custom period: audits a specific window reported by user or support.
- No filter: shows all available history, useful for overview but noisier.
- Event without response: can indicate offline device, pending command, or execution failure.
¶ How to interpret command results and timestamps
- IN_PROGRESS: the portal created and forwarded the command but is still waiting for a terminal result. This status does not confirm execution on the device.
- SUCCESS: the backend received successful completion feedback. This is a terminal status, but you should still verify the operational effect in the relevant screen when the action changes policy, network, apps, or data.
- ERROR: the device or provider returned a failure. This is a terminal status; review the error details, connectivity, command support, and current state before retrying.
- EXPIRED: the command validity ended without successful feedback. This is a terminal status and, by itself, does not prove that the device never received the request; check last sync before resending a destructive action.
- Start time → end time: the first time is the recorded creation/send time and the second is the displayed processing or feedback time. Equal values may be caused by minute-level display precision and do not mean zero latency.
- Refresh: reloads history to retrieve new results. It does not resend any listed command.
- Filters: only change which events are visible; they do not cancel, repeat, or modify commands.
The time filter helps limit the investigation to recent windows, custom ranges, or support- and audit-oriented time slices.
This area is used to track network events, synchronization, connection, disconnection or relevant changes that help in diagnosing offline or unstable devices.
¶ Screen elements
- Network events: record changes in connectivity, Wi-Fi, mobile data or lack of communication.
- Timeline: orders occurrences to support intermittent fault diagnosis.
- Relationship with last sync: differentiates device without internet from a policy or app problem.
- Supporting evidence: serves as a basis for guiding the user, operator or field team.
¶ What each option allows
- History tab: concentrates sent commands, device responses, failures, synchronization events, and connectivity records.
- Command filter: restricts analysis to event types, such as reboot, remote password, sync, report, or support actions.
- Time filter: limits investigation to recent windows, custom dates, or an incident interval.
- Timeline: helps correlate sent command, last communication, and received response.
- Correct use: first filter by the incident period, then by the command or event under investigation.
¶ Application in operation
- Read the timeline and compare times to user complaints or sent commands. Use history to differentiate network failure, lack of battery, no sync, or policy issue.
¶ Policy applied
¶ Policy applied screen
The Policy tab highlights which policy is linked to the device before opening the detailed version, synchronization, and applied-rules view.
The policy tab applied to the device.
This area is used to check which policy is linked, version applied, synchronization status, and information related to the current rule set.
¶ Screen elements
- Policy Name: shows which rule set is assigned to the device.
- Version or status: indicates whether the device is in the expected policy or awaiting update.
- Rules Summary: displays relevant settings applied to the equipment.
- Policy change: must be done carefully to avoid loss of access, apps or connectivity.
¶ How to prove application
- Name: is the policy the portal expects to be assigned to the device.
- Last sync: is the last policy synchronization time reported by the device; it is not the time when the administrator saved the policy.
- Policy version: is the version reported by the device. Application is proven when it matches the policy's current saved version and synchronization occurred after the change.
- Zero-Touch - Policy or provider: shows the assignment used by the provisioning provider. It may differ from the policy currently applied to the device.
- Zero-Touch - Last sync: confirms the last synchronization with the Zero-touch provider, not that the device applied the rules.
- On an offline device, the previous version remains effective until communication and successful synchronization occur.
¶ What each option allows
- Use Policy to confirm whether the device received the correct policy and whether the applied version matches the current saved version.
- Use System to validate Android, patch, manufacturer, network, and reported settings before concluding that a rule failed.
- When there is divergence, request report/sync and compare expected policy, last sync, and technical device data.
¶ Application in operation
- Check that the policy and version are as expected. To change, use the Change policy action. Then request a report or wait for synchronization to confirm that the new policy has been applied.
¶ System
¶ System screen
The System tab gathers the device's technical data and opens the system, hardware, network, and settings subareas for support and auditing.
The system tab with general Android and management data.
This area is used to query system version, security patch, identifiers, management mode and basic information required for support and auditing.
¶ Screen elements
- Operating System: shows Android version, patch level, and build information when reported.
- Manufacturer and model: identify the hardware platform used in the operation.
- Management State: confirms that the device is under expected corporate control.
- Technical data: are used for diagnosis, compatibility and auditing.
¶ What each option allows
- Use Policy to confirm whether the device received the correct policy and whether the applied version matches the published one.
- Use System to validate Android, patch, manufacturer, network, and reported settings before concluding that a rule failed.
- When there is divergence, request report/sync and compare expected policy, last sync, and technical device data.
¶ Application in operation
- Use this tab to validate compatibility, Android version, management status and identification data. Copy the relevant information when opening a technical ticket.
¶ Hardware
The hardware section of the device plug.
This area is used to consult the manufacturer, model, memory, storage, IMEI/serial and physical characteristics reported by the equipment.
¶ Screen elements
- Manufacturer/model: identifies the physical family of the equipment.
- IMEI, serial and identifiers: support inventory, warranty, blocking, chip and asset traceability.
- Battery and power: shows field operation capability and possible load failures.
- Memory and storage: helps identify lack of space or performance limitations.
¶ Application in operation
- Go to System > Hardware to confirm that the device matches the physical inventory. Use this data for auditing, warranty, equipment replacement, and capacity diagnostics.
¶ Network
The network section of the device plug.
This area is used to view information such as carrier, Wi‑Fi, MAC address, IP, SIM/eSIM or available connectivity data.
¶ Screen elements
- Wi-Fi: shows SSID, connection state, or used network when available.
- Mobile data: indicates carrier, SIM, roaming or reported cellular connectivity.
- Addresses and network identifiers: support troubleshooting with infrastructure and operators.
- Connection State: helps separate internet failure from policy or application failure.
¶ Application in operation
- Use to investigate communication, APN, Wi‑Fi, chip or mobile connectivity failures. Compare the information with the expected network policy and SIM/carrier.
¶ Settings
The system configuration section reported by the device.
This area is used to audit settings such as language, zone, lock status, system options, and collected technical parameters.
¶ Screen elements
- Settings reported: show state of resources controlled by policy.
- Disagreements: indicate when the device has not yet applied an expected rule.
- Technical details: support analysis of restrictions, permissions and management status.
- Support reference: serves to compare the device with others in the same group.
¶ Application in operation
- Use this section when a restriction does not appear to apply or when Android behavior differs from what you expect. Compare the reported values with the policy rules.
¶ Installed applications
¶ Installed applications screen
The Apps tab concentrates the list of applications present on the device and allows you to drill down into the details of each installed package.
The applications tab installed on the device.
This area is used to check apps present on the device, versions, origin, installation status and relationship with the applied policy.
¶ Screen elements
- App list: displays packages present on the device.
- Installed version: allows you to confirm updates, delays or discrepancies between devices.
- Origin and status: help differentiate managed, system, manually installed or removed app.
- Corrective Action: may involve installation, blocking, updating or removal policy.
When you open an individual application, the portal shows version, package identifier, and app event history, which helps validate updates, reinstalls, or unexpected behavior.
¶ What each option allows
- App detail: shows package, version, source, and information to confirm the installed app is expected.
- App history: helps understand installation, update, failure, removal, or unusual behavior.
- Policy comparison: shows whether the device version/status matches the rule defined in Policies > Apps.
- Corrective action: when there is divergence, adjust policy, version, permissions, or connectivity and request a new report.
¶ Application in operation
- Search for the app by name or package. Check version and status. If the app should be installed or removed, adjust the app policy and monitor the sync.
¶ Location
¶ Location screen
The Location tab organizes the device position history and serves as the basis for tracking, route review, point-in-time location, and geolocation requests.
The device location tab with map and history/reported points.
This area is used to track the last known position and, when available, the location history of the equipment.
¶ Screen elements
- Last Position: shows the most recent location reported by the device.
- Map: allows you to interpret the position in the operational territory.
- Collection date: indicates whether the information is recent or historical.
- History: supports route investigation, loss, theft, improper displacement or field service.
The location card highlights collection date and time, approximate address, and shortcuts to open the point in Google Maps or trace the route using the latest recorded points.
¶ Result of selections and settings
- Request geolocation: sends a request to collect a new device position.
- Online device: tends to respond faster, depending on permissions and policy.
- Offline device: the request may remain pending or return no position.
- Location disabled: prevents update until policy/permission allows collection.
- Updated point: replaces or complements the latest visible map position.
- Request failure: investigate connectivity, location policy, and data collection.
When the displayed point is outdated, the Request geolocation button can ask the device for a fresh collection, depending on connectivity, permissions, and location policy.
¶ What each option allows
- Map point: shows where the device reported location and allows validation against the expected area.
- Location card: displays date, time, approximate address, and map/route shortcuts.
- Request geolocation: requests a new collection when the position is outdated, if the device is online and authorized.
- History: supports route, loss, theft, unauthorized movement, or field support investigations.
- Prerequisite: depends on location policy, permissions, connectivity, and enabled collection.
¶ Application in operation
- Access the Location tab, select the desired period or point and navigate the map. If there is no data, confirm collection policy, permissions, connectivity and use of the geolocation helper app when applicable.
¶ Allocation
¶ Allocation screen
The device allocation tab, with user, group, policy, tags or administrative fields.
This area is used to organize equipment within the operation, linking it to the person responsible, branch, customer, policy group or internal information.
¶ Screen elements
- Linked user: links the equipment to the person responsible, collaborator or operational identity.
- Group: defines the administrative segmentation used in filters, reports, and policies.
- Associated policy: determines which rules the device should receive.
- Asset data: supports stock control, delivery, collection and auditing.
¶ Result of selections and settings
- Allocated: device in use by active user/operation.
- Borrowed: temporarily loaned device, useful for return tracking.
- Stock: device available in inventory, usually out of operation.
- Maintenance: device under repair, diagnosis, or temporarily unavailable.
- Discontinued: device retired, discarded, or at end of life.
- Incorrect status: harms filters, reports, operational billing, and bulk actions.
The status field lets you quickly classify the asset lifecycle, with options such as Allocated, Borrowed, Stock, Maintenance, and Discontinued.
¶ What each option allows
- Allocated: indicates a device delivered or linked to an active user/operation.
- Borrowed: identifies temporary loan and helps track return.
- Stock: keeps the asset in inventory, with no current operational use.
- Maintenance: separates devices under repair or diagnosis.
- Discontinued: marks an asset out of use, retired, or at end of life.
¶ Application in operation
- Edit the allocation fields according to your company's process. Use groups and tags in a standardized way to facilitate filters, reports, permissions and bulk actions.