# On-board edge devices

Prepare an edge device, connect it to MK.IO, and register it to a project. Choose the onboarding path that matches how the installer can access the device.

## On-boarding paths

Different network environments call for different on-boarding approaches. Choose the path that fits your setup:

- [Common workflow](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/common-workflow): Set the device Control interface IP, connect to the device web UI, copy a short code, and enter it in MK.IO.
- [On-boarding via device terminal only](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/terminal-only): Use when the installing engineer cannot access the device web UI. Obtain the Device ID from the terminal and register using the MK.IO UI.

* [On-boarding via API](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/api-onboarding): Register the device using the MK.IO API instead of the MK.IO UI. The device must still have internet access.
* [Removing devices](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/remove-device): How to remove an edge device from MK.IO using the UI or API.

- [Troubleshooting](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/troubleshooting): How to troubleshoot common issues when on-boarding edge devices.

Use the [Fleet device management API Guide](/api-guides/how-to/fleets/device-management) to register, inspect, update, or remove devices through the Fleet API.