Enrol Android devices

Once Android MDM is connected, you enrol devices by generating a QR code and scanning it during a device's first-time setup.

You'll need the mdm.enrol permission.

Generate an enrolment code

1. Go to Settings → MDM → Devices (or Manage devices from the MDM settings page).
2. Click Enrol device.
3. Pick the management mode:
   • Fully managed - a company-owned device, enrolled from factory reset. The default.
   • Work profile (BYOD) - an employee-owned device. No factory reset: you get an enrolment link to send to the user; opening it installs a separate managed work profile and their personal apps and data stay private. Only the BYOD policy rule and work-profile-scoped rules apply.
   • Dedicated device - a userless kiosk (till, signage, scanner). Enrols from factory reset like fully managed; pair it with the Kiosk policy rule.
4. Optionally pick the client / site the device belongs to. The device attaches to that site automatically when it first checks in, and picks up the site's default policy from the outset.
5. Optionally pick a Wi-Fi network for setup. The network is embedded in the QR code, so the device joins it during setup without any manual typing. Save networks once under Manage saved Wi-Fi networks in the same dialog; passwords are stored server-side and never shown again.
6. Click Generate QR code. OpsMerge generates a QR code and a short manual code (or, for BYOD, the enrolment link).
7. Keep this dialog open while you set up the device — the code expires after an hour.

Enrol the device

The device must be factory reset (or new out of the box).

Tell the device's users

Enrolled devices are fully managed: policies control apps, settings, and (if enabled in the policy) location reporting. Android shows its own "this device is managed" notice during setup, but you should also tell whoever uses the device that it's managed and what's collected - your customer agreement requires their users to be informed.

1. On the welcome screen, tap the same spot six times to open the QR scanner.
2. Scan the QR code from OpsMerge. If the code carries a Wi-Fi network the device joins it automatically; otherwise connect to Wi-Fi when prompted. The device downloads Android Device Policy and provisions itself.

Can't scan? Enter the manual code instead when the device asks for it (you'll need to join Wi-Fi manually in that case).

After enrolment

The device appears in the Devices list within a few minutes, with its model, OS version, and compliance state. Devices enrol onto a minimal bootstrap policy so setup can never fail on app installs; once the device finishes provisioning, OpsMerge automatically moves it to the site's default policy (or the organisation default). You can still assign a different policy or issue commands (lock, reboot, lost mode on, lost mode off, reset passcode, wipe) from the device's detail page. Commands are refused while the device is still provisioning.

Device details refresh automatically every five minutes. If a freshly enrolled device shows sparse details (a device still provisioning often has no hardware identity yet), use the refresh button on its detail page, which pulls the device straight from Google rather than waiting for the next sync. The Compliance tab also lists recent webhook events for the device, so you can see whether Google notifications are arriving and being processed.

Billing

Each enrolled device counts as a billable mobile device asset, so it appears automatically on the client's recurring invoice once you assign the device to a site. Releasing or wiping a device stops its meter.