NomidPrepare your fleet
Get the device ready for the work ahead.
Decide how it joins the fleet, define its role, and give it the apps and content it needs before handoff.
Three connected decisions
A useful rollout is designed before the first handoff.
How will it join the fleet?
Choose the supported path for company-owned, personal, or eligible VR devices.
What should it do?
Put apps, network, restrictions, and the device experience into a policy.
What should it carry?
Organize the apps, links, files, and other resources behind that role.
Before scaling
Pilot on the real device. Then repeat.
Hardware, Android version, management mode, and connectivity can change the result. Test the exact policy and content on a representative device, and confirm its behavior in Nomid before a broader rollout.
Plan the enrollment pathQuestions before setup.
Where should I start?
Start with the device’s ownership and job. Then choose a supported enrollment path, prepare the policy, and add the apps or content the device needs.
Can I set up personally owned and company-owned devices together?
Nomid presents separate enrollment paths for company-owned Android devices and personally owned devices. Their management controls differ, so pilot each ownership model separately.
What about VR headsets?
The Portal has a dedicated VR setup path where access is enabled. Confirm the supported headset and policy options with Nomid before planning a rollout.
Start with your
first device.
Explore Nomid with your own devices, or plan your deployment with our team.