¶ ¶ User Manual — Devices
Application or layer: Portal Nomid MDM
Document: V1.0.0
Last updated: 17/06/2026
Language: en_US
The Devices module centralizes the inventory and operation of devices managed by Nomid MDM. It is possible to consult the fleet, switch between list and map, apply filters, open a device's file, perform remote actions, monitor usage, applications, applied policy, system information, location and allocation.
Important: Some actions require the device to be online or resync with the Android Device Policy/management agent. If the command is pending, validate connectivity, battery, applied policy and last report.
¶ ¶ List and map
¶ ¶ Toggle list or map
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.
¶ ¶ Featured 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.
- State preserved: the chosen view helps maintain the operator's workflow.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
¶ ¶ 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.
¶ ¶ Featured elements
- Device lines: represent each equipment registered in the tenant.
- Inventory columns: display identification, status, policy, group, user, model and last communication according to availability.
- Item selection: enables bulk actions for groups of devices.
- Access to the card: the name, identifier or card of the device opens the complete details.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
¶ ¶ 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.
¶ ¶ Featured elements
- Markers: indicate the last location reported by the 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, without location collection or without valid permission/report.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The Devices home screen can be displayed in list or map format.
¶ ¶ List
The list is suitable for administrative operation, auditing and device selection. It allows you to compare fields such as name, model, status, IMEI, serial number, policy, group, last synchronization and other available attributes.
¶ ¶ Map
The map is suitable for geographic analysis. It presents the last known location of devices with available location collection.
Attention: The accuracy of the map depends on the collection of geolocation, permissions, connectivity, GPS/network and the last synchronization of the equipment.
¶ ¶ 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.
¶ ¶ Featured 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 the analysis by status, group, policy or condition.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
Search finds devices by terms such as name, IMEI, serial number, model, status, policy, group or tags. When available, AI-assisted search helps transform a description into filters.
¶ ¶ Useful examples
- Search for a specific IMEI.
- Find devices from a model.
- Find equipment associated with a policy.
- Search by branch, client or project tags.
¶ ¶ Filters
¶ ¶ Filters
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.
¶ ¶ Featured 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 operational segment.
- Policy: only shows devices associated with a specific rule.
- Model or system: helps investigate problems focused on manufacturer, Android version or device type.
- Clear filters: returns to the full view after analysis.
¶ ¶ Operational guidance
- 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.”
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
Filters refine the listing and reduce operational noise.
¶ ¶ Common filters
- IMEI: locates devices by mobile identifier.
- Serial Number: locates by serial number.
- App installed: filters devices with a certain application.
- Policy: shows devices linked to a policy.
- Policy Groups: shows devices by policy group.
- Last sync before: identifies devices without recent sync.
- Status: separates active, inactive, pending or equivalent states.
- MAC Address: locates by network address.
¶ ¶ Columns
¶ ¶ Columns
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.
¶ ¶ Featured 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 tenant.
- Routine customization: allows you to create a leaner view for support, inventory or auditing.
¶ ¶ Operational guidance
- Select Columns, activate or deactivate the fields and rearrange the view as necessary. For support analysis, prioritize status, last sync, policy, model, IMEI and relevant apps.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The column selector allows you to choose which information appears in the list.
¶ ¶ Recommended use
- For support: view status, latest report, policy and template.
- For inventory: display IMEI, serial number, brand, model and user/allocation.
- For audit: View compliance, policy, policy version, and last sync.
¶ ¶ Saved Views
¶ ¶ Saved Views
The devices screen saved views menu.
This area is used to save filter, column, and view combinations for reuse in operation routines.
¶ ¶ Featured elements
- View: saves combination of filters, columns and ordering for reuse.
- Support view: can prioritize status, last sync and diagnostic actions.
- Inventory view: can prioritize IMEI, serial, model, user and group.
- Operational sharing: standardizes the way different operators analyze the fleet.
¶ ¶ Operational guidance
- Configure filters and columns, open Views and choose Save current view. Use saved views to track offline devices, equipment by customer, or recurring audits.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
Views allow you to save a set of filters, columns and visualization form to reuse later.
¶ ¶ View examples
- “Devices not syncing for more than 7 days”.
- “Logistics fleet”.
- “Devices with maintenance policy”.
- “Equipment from a specific branch”.
¶ ¶ Device card
¶ ¶ Device card
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.
¶ ¶ Featured 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 details: opens the complete file for diagnosis and remote actions.
¶ ¶ Operational guidance
- Click on 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The card summarizes important device information without having to open the full file.
¶ ¶ Information normally displayed
- Device name or identifier.
- Model and manufacturer.
- Management and security status.
- Policy applied.
- Last location or last sync.
- Shortcuts to open the device or perform actions.
¶ ¶ Actions by device in the list
¶ ¶ Device actions in list
The actions menu for a device in the listing.
This area is used to open the device page, change policy or perform sensitive actions such as wipe/remove, depending on permissions.
¶ ¶ Featured 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 or group: changes the administrative framework of the asset when authorized.
- Remote commands: perform actions such as synchronize, lock, restart, clear password or erase, depending on device permissions and support.
- Destructive actions: must be confirmed carefully as they affect data or availability.
¶ ¶ Operational guidance
- Access the Actions menu on 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The actions menu allows you to execute commands directly on a selected device.
¶ ¶ Common actions
- Open Device Page: opens the complete device page.
- Change policy: changes the policy applied to the equipment.
- Wipe and remove: erase/remove the device from management, when allowed.
Attention: Destructive actions, such as wipe/remove, must only be used with confirmation from the person responsible. This action may erase data from the device and disrupt end-user operation.
¶ ¶ Bulk actions
¶ ¶ Bulk actions
The bulk actions menu after selecting devices.
This area is used to apply commands to various devices, such as changing policy, sending report, restarting, blocking, clearing password or removing, according to tenant availability.
¶ ¶ Featured elements
- Multiple selection: allows you to select multiple devices before performing an action.
- Batch application: reduces operation time when changing policy, group or administrative commands.
- Selected scope: must be reviewed before confirmation to avoid impact on wrong devices.
- After-action follow-up: must be done through the status, last sync and history of the affected devices.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
Bulk actions allow you to operate multiple selected devices at once.
¶ ¶ Examples
- Change policy in batch.
- Execute remote commands on multiple devices.
- Export or organize selected devices.
- Remove deactivated equipment.
Best practice: Before performing a bulk action, apply filters to ensure only the correct devices are selected.
¶ ¶ General actions
¶ ¶ General actions
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Use New device to start registration/provisioning, Import Devices for batch loading and Export as .xlsx to generate a spreadsheet with filtered/visible devices.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
General actions are at the top of the screen.
¶ ¶ Options displayed
- Export as .xlsx: exports the list or filtered result to a spreadsheet.
- Import Devices: imports devices from a supported file or stream.
- New device: starts the registration/provisioning of a new device.
- Actions: groups administrative commands available for the current context.
¶ ¶ Device sheet — Summary
¶ ¶ Device Summary
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Access the device through the list and read the summary before executing any command. Use the links, cards and side tabs to delve deeper into usage, system, apps, location and allocation.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The device sheet presents a complete overview of the equipment. The Summary tab shows the main identification, status and management data.
¶ ¶ What to check first
- Device status.
- Last check-in/last report.
- Policy applied.
- Group or allocation.
- Model, system and connectivity information.
- Safety/compliance indicators.
¶ ¶ Individual actions on the sheet
¶ ¶ Individual actions
The individual actions menu available within the device tab.
This area is used to execute remote commands on specific equipment, such as restart, lock screen, clear/change password, request report, change policy, synchronize, send message or remove/wipe.
¶ ¶ Featured elements
- Actions: opens specific commands for the device under analysis.
- Sync: requests status update and policy application when available.
- Block or restart: supports operational support and containment.
- Change link: adjusts user, group, policy or allocation according to permissions.
- Delete data: should be reserved for loss, theft, disposal or serious incident.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The plug menu allows more specific commands for the open device.
¶ ¶ Command examples
- Manage policies.
- Force sync or status update when available.
- Lock screen.
- Reboot device, when supported.
- Change password or clear password, depending on Android version and management mode.
- Send message to user.
- Erase/remove device.
Note: Support for each command depends on management mode, Android version, manufacturer, and policy permissions.
¶ ¶ Device usage
¶ ¶ Device usage
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Choose the desired period and read the charts. Use usage spikes as a trigger to investigate apps, user, location, or need for policy adjustment.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The usage tab shows aggregated equipment usage data for the selected period.
¶ ¶ What is it for
- Validate whether the device is being used.
- Identify periods of activity and inactivity.
- Compare screen, data and app usage.
- Support investigation of improper consumption or operational failures.
¶ ¶ Usage by application
¶ ¶ Use per application
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.
¶ ¶ Featured elements
- App list: shows the applications that have registered use on the device.
- Time per application: indicates which apps concentrate the user's 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.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The application view lists consumption and usage time per app.
¶ ¶ How to analyze
- Corporate apps must appear according to the purpose of the device.
- Unexpected apps may indicate a need to review the policy.
- High data consumption may indicate synchronization, media, updates or misuse.
¶ ¶ App Usage Detail
¶ ¶ App Usage Detail
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.
¶ ¶ Featured elements
- Selected application: identifies the package analyzed individually.
- Detailed metrics: present 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.
¶ ¶ Operational guidance
- Select an app from 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The details of an app allow you to analyze individual behavior, such as variation in consumption and activity over time.
¶ ¶ When to use
- When an application appears as the largest consumer of data.
- When there is suspicion of misuse.
- When a specific version of the app has a problem.
- When it is necessary to prove the use of a corporate tool.
¶ ¶ Connectivity and operational events
¶ ¶ Connectivity and events
The device's connectivity/events tab, with history of changes and reported signals.
This area is used to track network events, synchronization, connection, disconnection or relevant changes that help in diagnosing offline or unstable devices.
¶ ¶ Featured 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 a device without internet from a policy or app problem.
- Supporting evidence: serves as a basis for guiding the user, operator or field team.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
This area presents additional information on connectivity, events and operational status of the device.
¶ ¶ Analysis examples
- Connection changes.
- Battery or power events.
- Network changes.
- Signs of instability that explain lack of synchronization.
¶ ¶ Policy applied
¶ ¶ Policy applied
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Check if 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The Policy tab shows the policy applied to the device and compliance information.
¶ ¶ Important fields
- Name of the policy.
- Version applied.
- Application status.
- Any errors or pending issues.
- Relationship with current group/politics.
Tip: If a device does not behave as expected, compare the policy version applied to it with the current policy version in the Policies module.
¶ ¶ System
¶ ¶ System
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Use this tab to validate compatibility, Android version, management status and identification data. Copy the relevant information when opening a technical ticket.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
¶ ¶ 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.
¶ ¶ Featured 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: show field operation capability and possible load failures.
- Memory and storage: help identify lack of space or performance limitations.
¶ ¶ Operational guidance
- Go to System > Hardware to confirm that the device matches the physical inventory. Use this data for auditing, warranty, equipment replacement, and capacity diagnostics.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
¶ ¶ 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.
¶ ¶ Featured elements
- Wi-Fi: shows SSID, connection state or network used when available.
- Mobile data: indicates operator, 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.
¶ ¶ Operational guidance
- Use to investigate communication, APN, Wi‑Fi, chip or mobile connectivity failures. Compare the information with the expected network policy and SIM/carrier.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
¶ ¶ Configuration
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.
¶ ¶ Featured elements
- Settings reported: show status 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.
¶ ¶ Operational guidance
- Use this section when a restriction does not appear to apply or when Android behavior differs from what is expected. Compare the reported values with the policy rules.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The system tab gathers technical information reported by the device.
¶ ¶ General
- Brand, model and manufacturer.
- Android version.
- Serial number.
- State of security and encryption.
- Management information.
¶ ¶ Hardware
- Hardware model.
- Storage and memory capacity.
- Equipment identifiers.
- Battery information when available.
¶ ¶ Network
- Main and secondary IMEI, when available.
- Operator/SIM.
- Telephone number, when reported.
- MAC Wi-Fi and connectivity data.
¶ ¶ Configuration
- Unknown sources.
- Encryption.
- Screen/password protection.
- Developer mode and ADB.
- Checking apps and other Android states.
¶ ¶ Installed applications
¶ ¶ Installed applications
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.
¶ ¶ Featured 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, update or removal policy.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The Apps tab lists the applications installed or managed on the device.
¶ ¶ What to watch out for
- Application name and package.
- Installed version.
- Origin of the app.
- Installation status.
- Managed permissions and settings when available.
¶ ¶ Practical use
Use this tab to confirm whether a required app has been installed, whether a blocked app still appears on the device, or whether the installed version is different than expected.
¶ ¶ Location
¶ ¶ Location
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- 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.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The location tab displays the device's history or last known position.
¶ ¶ Features
- Map with location points.
- History by date/time.
- Indication of accuracy, when available.
- Shortcut for geographic analysis.
Attention: Location collection must be enabled in the policy and depends on device permissions and behavior.
¶ ¶ Allocation
¶ ¶ Allocation
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.
¶ ¶ Featured 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.
¶ ¶ Operational guidance
- Edit the allocation fields according to the company's process. Use groups and tags in a standardized way to facilitate filters, reports, permissions and bulk actions.
- Before saving, publishing, or running commands, confirm that the selected company, group, policy, or device matches the desired scope.
The Allocation tab relates the device to responsible parties, groups, users, units, locations or internal inventory information.
¶ ¶ What is it for
- Know who or where the equipment is owned.
- Support asset control.
- Relate device to operation, branch or customer.
- Facilitate support when there is a change of user or movement of stock.
¶ ¶ Recommended investigation flow
- Search the device by IMEI, name or serial.
- Check status, latest report and applied policy.
- Open the Policy tab and validate compliance.
- Check System > Network under Chip/Data issues.
- Check Apps for app issues.
- Check Usage and Location for suspected misuse or loss.
- Only execute destructive commands after confirming that the correct device has been selected.