Platform · Mobile Device Management

Android Mobile Device Management (MDM)

Manage Android Enterprise device profiles, enrollment, device inventory, compliance and authorized remote controls. Android Enterprise setup, device policies, enrollment, remote control, compliance, and fleet oversight.

In short

MDM administers eligible Android devices through the company’s configured Android Enterprise integration, policies, enrollment, inventory, commands, compliance, applications, and fleet reporting.

What it does

Mobile Device Management

01

Connect Android Enterprise

Configure the company’s supported Google integration and Android Enterprise binding.

02

Publish a device profile

Define the device policy and supported management mode before enrolling the staff device.

03

Enroll with a QR code

Issue an enrollment token linked to the published profile and use it to enroll the device.

04

Review the device fleet

Inspect enrolled device inventory, assigned-user context, reported state, and available compliance information. Remote controls depend on the enabled release and permissions.

How it works

The devices supporting field work have a company-owned configuration, enrollment, and administrative history.

  1. Configure the company integration and publish a device profile.

  2. Create the enrollment token and enroll the Android device.

  3. Review the device in the company-scoped inventory.

Features

29 features

29 named features across the areas below.

Enterprise and device profiles

6 features

Prepare the company’s Android management context before enrollment.

  • Company Google integrationConfigure the supported Google API client and company Android Enterprise binding.
  • Profile templates and inheritancePrepare profiles from supported parent/template/own-setting layers.
  • Guided policy settingsConfigure the supported screen-lock, camera, capture, USB, update, location, and kiosk controls.
  • Management modesChoose a supported fully managed, dedicated, company work-profile, or personal work-profile enrollment mode.
  • Profile revision and approvalReview profile versions and the configured approval requirement before publishing.
  • Policy publicationPublish an eligible profile to the configured Android Enterprise environment.

Enrollment and device inventory

6 features

Follow the device from enrollment token to company asset.

  • Enrollment tokens and QR codesIssue the supported enrollment token linked to the chosen profile and management mode.
  • Token states and usageReview the supported expiry, use, and one-time-token exhaustion state.
  • Device inventoryReview the reported model, serial, platform version, patch, battery, storage, policy, and last-seen context.
  • Asset and assigned-user contextMaintain the company’s asset tag, assigned user, tags, and notes.
  • Scheduled and live synchronizationUse the configured Google sync or supported Pub/Sub notifications.
  • Inactive-device monitoringReview devices that have not reported within the configured threshold.

Commands and lost-mode tracking

6 features

Apply administrative device actions through the permitted controls.

  • Lock and rebootSend the supported remote device-control commands with their result history.
  • Lost mode and location historyStart/stop supported lost mode and inspect the permitted reported positions.
  • Password and app-data commandsUse supported reset-password and clear-app-data actions for eligible devices.
  • Ownership and unenrollment actionsUse the supported relinquish or wipe/unenroll operation with its required confirmation.
  • Bulk commandsSend supported actions to selected devices and review individual failures.
  • Command result monitoringDistinguish submitted, acknowledged, succeeded, failed, and expired command states.

Compliance, apps, and fleet reporting

11 features

Review policy findings and the configured response.

  • Compliance rulesConfigure the supported device conditions, severity, and remediation behavior.
  • Findings and exceptionsReview Google/local findings and record the supported temporary exception with a reason.
  • Controlled remediationApply the configured notification, lock, or wipe response with the required approval boundaries.
  • Managed application assignmentsConfigure supported package installation, permissions, update, and managed-configuration settings.
  • Application publication statusReview draft, published, or error states and republish the profile when app assignments change.
  • Mobile app build distributionDownload the latest Android app or an earlier retained build using a private, expiring link or device-scannable QR code.
  • Build integrity and historyReview the build number, version, release notes, file size, and SHA-256 fingerprint for the four retained builds.
  • Device groupsMaintain supported manual or dynamic fleet group membership.
  • Fleet reports and usageReview the supported inventory, compliance, device, and usage reporting.
  • Saved fleet reportsPrepare scoped CSV exports, schedule daily/weekly/monthly delivery, and review generation and email delivery status.
  • Audit historyTrace configuration, publication, token, synchronization, device, and command changes.

Worked example

Policy, enrollment, findings, and commands

Device management depends on Google integration, device eligibility, management mode, and the authorized action.

Administrative objectWhat it establishesWhat it does not establish
Published profileThe intended device policyThat every enrolled device has applied the latest policy.
Enrollment tokenThe profile and management-mode entry pointA compliant, recently synchronized device.
Compliance findingA condition requiring the configured review/remediationPermission to bypass the required wipe or lost-mode confirmation.
Submitted commandA request accepted for processingA successful device outcome until the result reports it.

What you get

What you get

  • Published policies and enrollment records

  • Company-scoped device inventory

  • Remote-command and compliance results

  • Fleet/app/group reports and audit history

What is Mobile Device Management?

MDM administers eligible Android devices through the company’s configured Android Enterprise integration, policies, enrollment, inventory, commands, compliance, applications, and fleet reporting.

How does an Android device enter management?

Prepare the company integration and Android Enterprise binding, publish an appropriate profile, issue an enrollment token for the intended ownership mode, and enroll the device using the supported QR/token flow.

Does a submitted remote command mean the device completed it?

No. Submitted, acknowledged, succeeded, failed, and expired states describe different outcomes. Inspect the reported device result instead of treating acceptance of the request as execution.

What is required before an Android device can be enrolled?

The supported setup needs the company’s Google API integration and Android Enterprise binding, a published suitable profile, and an enrollment token for the intended management mode.

Does wiping a personal work-profile device have the same scope as a company-owned device?

The supported ownership/management mode determines the operation. Review the eligible work-profile versus company-device action, its permissions, and the required confirmation before authorizing it.

Book a demo

See Prospiro run your own process.

Tell us what you sell, stock and deliver. We plan the session around the modules you need, in English or Arabic.

  • Built around your products, routes and documents
  • Includes the exceptions, not only the happy path
  • Your request goes straight to our team

Prefer email? info@prospiro.ai

What do you want to see?
We use your details only to reply to your request and follow up on it. Privacy policy
VAT calculator