Mobile devices
Mobile device management for Apple and Android
For MSPs who want customer phones and tablets in the same workspace as their computers. Apple iPhone and iPad management is in use with our first design partner. Android Enterprise is built and starts once your Google connection is set up.
What it does
Enroll, apply policy, act when a device is lost.
01 / APPLE
Apple enrollment.
Enrollment profiles for iOS and iPadOS, with devices checking in through Apple push notifications.
02 / APPLE
Apple profiles.
Passcode, restriction and Wi-Fi profiles pushed to enrolled devices.
03 / APPLE
Apple actions.
Refresh a device's details, lock it, or erase it.
04 / ANDROID
Android enrollment.
Enrollment by QR code, with policy pushed to the device once it joins.
05 / ANDROID
Android actions.
Lock, reboot or wipe a managed Android device.
06 / PORTAL
Visible to the customer.
Enrolled devices show in your management view and in that customer's own portal, under mobile devices.
Status
Where each platform stands today.
APPLE IOS AND IPADOS
In field use.
Needs: your own Apple push certificate. Works: enrollment profiles, push check-in, passcode, restriction and Wi-Fi profiles, refresh, lock and erase. Field use: in use with our first design partner.
ANDROID ENTERPRISE
Built, not yet used in the field.
Needs: your workspace's own Google service account and enterprise, connected before any device can enroll. Works: QR enrollment, policy push, lock, reboot and wipe. Field use: none recorded yet.
How it works
From an email to a managed device.
01
Create the enrollment
Enrollments belong to a customer, so the device lands in the right organization from the start.
02
Send it
Email the user an enrollment link, or hand them a QR code. The landing page walks them through it.
03
It enrolls and takes policy
The device checks in, inherits its customer, and starter policies apply automatically.
04
It appears where it should
The device shows in your management view and in that customer's own portal.
Limits
What it does not do yet.
Limits
- Android Enterprise is built but has not yet been used in the field.
- Each workspace must connect its own Google service account and enterprise before any Android device can enroll.
- Apple management needs your own Apple push certificate.
- Not for you yet if you need a large Android fleet under management on day one. Start with Apple devices, and talk to us about Android first.
Not in the product today: one connected asset record across agent, network, mobile and manual sources, and verified offboarding.
Questions
Good to know.
Your own Apple push certificate. After that you can send enrollment profiles and push passcode, restriction and Wi-Fi profiles.
Your workspace connects its own Google service account and enterprise. Until that connection is in place, Android devices cannot enroll.
Not yet. It is built, but no field use is recorded. Talk to us before you rely on it for a customer fleet.
Yes. Apple devices can be locked or erased. Android devices can be locked, rebooted or wiped.
Yes. Enrolled devices appear in that customer's own portal, under mobile devices.
Keep exploring
Limits, checked daily
Not in the product today.
Each line below is a gap recorded against this capability in the product's own feature record. A line leaves this page by itself on the next daily run once that record says the gap is closed, so the list cannot fall behind what we ship. The rest of this page is written by hand.
- There is no lost mode that tracks the location of a missing device.
- Apple devices enroll, take profiles and can be locked, wiped and erased; automated device enrollment, managed app purchasing, disk encryption through management and kiosk modes are not built yet.
- Android devices take policies and can be locked, restarted and wiped; kiosk mode, location and remote viewing are not built yet.
Next step
Tell us about your customers' device mix.
Half an hour on a call. We will walk through enrollment and management for the devices you actually support.
