NomidQR code
Provision a supported company-owned device during its initial setup.
Android Enterprise enrollment
A better fleet starts with the first device.
Choose the right enrollment path for each Android device, connect its policy, and see it arrive in Nomid.
Start with ownershipTwo paths into a managed fleet.
NCompany deviceManaged for its role
Company-ownedFull management for dedicated workQR code or eligible zero-touch
NPersonal deviceWork in its own space
Personally ownedWork profile, personal space intactSupported work-profile enrollment
Illustration of enrollment paths; no QR code or credential shown.
Product film
From the device list to its location
Open a device and check where it has been, in two clicks.
The first decision
The device determines the path.
A company-owned device can be configured for a defined role. A personally owned device needs a separate managed work profile. Nomid presents those paths separately so the controls match the ownership model.
Company-owned
Start with a new or factory-reset device. Choose a policy before provisioning with a protected QR code or eligible zero-touch configuration.
Personally owned
Give supported personal devices a managed work area without treating the owner’s entire device as corporate hardware.
One rollout can need more than one method.
Choose by ownership, device state, Android version, and eligibility. Pilot the exact combination before a wider rollout.
Zero-touch
Connect an eligible, reseller-registered device to its assigned configuration.
Work profile
Create a managed work area on a supported personal device.
The first-device test
A device appearing is the beginning, not the finish.
Confirm that the intended policy and apps reach one representative device before scaling. Enrollment secrets stay protected throughout the process.
01Choose its policyDefine what belongs to the role.
02Provision safelyUse the eligible path for that device.
03Check the resultVerify the policy on the real device.
Illustrative first-device checklist
Questions before you enroll.
What is zero-touch setup and how does it work?
Android zero-touch enrollment lets an eligible company-owned device retrieve its assigned management configuration during initial setup. Device and reseller eligibility, internet access, and a valid zero-touch configuration are required.
Can I use different setup methods for different device types?
A deployment can combine QR code and zero-touch enrollment where each method fits the device's ownership model, state, Android version, and eligibility. Confirm those requirements before assigning a method to a rollout.
How secure is the setup process?
Treat enrollment tokens and QR codes as sensitive credentials. Limit who can access them, use only approved setup channels, retire credentials that are no longer needed, and verify the enrolled device before assigning production access.
What happens if setup fails?
Check the device's network connection, enrollment-token validity, Android version, ownership mode, and method eligibility. Retry with a valid configuration or choose another supported method, then confirm that the device appears in Nomid before applying production policies.
Can I customize what happens during setup?
You can choose the policies, managed apps, networks, and supported settings applied after enrollment. The available controls depend on the selected Android Enterprise management mode, device, Android version, and Nomid support.
How long does setup typically take?
There is no fixed setup time. Duration depends on the enrollment method, network, device, Android version, policy size, and number of managed apps. Pilot the exact configuration on representative devices before scheduling a larger rollout.
Before you enroll
Plan the first device, then repeat the path
Choose the ownership model and enrollment method before you scale a rollout.
Have ready
- Identify whether devices are company-owned, personal, or dedicated to one task.
- Have a test device and the policy it should receive ready.
Try the first device
- Use the planner to compare the available Android enrollment paths.
- Prepare the policy and follow the matching new-device flow.
- Enroll one device and check its assigned policy and apps before the wider rollout.
What to verify
The supported path depends on device ownership, setup state, and Android Enterprise support. A successful test device is the next check before fleet rollout.
Read the new-device guide
Start with your
first device.
Explore Nomid with your own devices, or plan your deployment with our team.