NomidDevice commands
Take action. Then see what happened.
Choose an available device action in context, send the request, and return to its history for the result. A command is only useful when you can follow it through.
Nomid records the request.
Execution depends on device conditions.
Product film
Send a command from a policy
Pick a device from the policy's device list and lock its screen.
Follow the action
Sent is a state. Done is a result.
The device might be offline or unable to execute an action. Keep a clear record of what you requested and what the device later reported.
The action enters the device workflow.
Read command history before declaring it complete.
Actions with a purpose
Choose the right action for this device.
Availability and effect vary by management mode. Review the device and the impact before sending a request.
Restrict access when a managed device needs attention.
Request a restart when the device supports it.
Ask for a fresh report before deciding what comes next.
Review the target and mode before a destructive request.
Practical details
Questions before you begin.
Which commands can I send?
Nomid exposes device actions such as lock, reboot, status report, and company-data wipe in the relevant Portal flows. Availability depends on the device and management mode.
Does sending a command mean it was executed?
No. A submitted request and a device result are different states. Use the command history and device status to investigate delivery or execution; an offline device cannot respond immediately.
How should I handle destructive actions?
Review the target device and command carefully before confirming an action such as a wipe. Its effect depends on the management mode and the command used.
Start with your
first device.
Explore Nomid with your own devices, or plan your deployment with our team.