Start with enrolling one device.
Everything else in the console makes more sense once there is a real handset in it. Fifteen minutes, one factory-reset device, one QR code.
Create a device group and get a code
Sign in, make a device group for the site or the job, and open Enrollments. The console gives you a QR code tied to that group.
Scan it from a factory-reset device
Factory-reset the Android device, tap the first setup screen a few times to bring up the scanner, and scan. The device installs the Mobility agent and registers itself.
Set a policy and an agent config
Set both on the group, not the device. Choose what the device may do, and which apps its home screen offers. The next device you enrol inherits all of it.
Guides by module
The console's own left-hand navigation, documented in the same order you will meet it.
Thirty widgets and how to arrange them.
Device detail, presence, history, cloning.
Bulk restart, message and unenrol.
Drawing areas and setting zone alerts.
QR codes, bulk import by serial.
Around 70 controls and what each needs.
Uploading APKs, versions, web apps.
Kiosk home screen, sign-in, check-in.
Sixty reports and how to export them.
Permissions and device-group scoping.
Storage and metered data, month by month.
Email, notifications, retention, push.
Support
Trouble signing in, an enrolment that will not complete, or a device behaving oddly. Tell us the serial number and what you expected to happen.
Contact supportStatus
Whether the console, the device agents and remote control are running normally. Check here before raising a ticket.
Ask supportThe device side
Four Android apps make up the device side: one agent and three companions for remote control, app inventory and the file manager. They install themselves at enrolment.
Agent reference