> This page is for mk.io.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://mediakind.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mediakind.ferndocs.com/_mcp/server.

# 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:

[](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/common-workflow)

### Common workflow

Set the device Control interface IP, connect to the device web UI, copy a short code, and enter it in MK.IO.

[](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/terminal-only)

### On-boarding via device 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.

[](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/api-onboarding)

### On-boarding via API

Register the device using the MK.IO API instead of the MK.IO UI. The device must still have internet access.

[](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/remove-device)

### Removing devices

How to remove an edge device from MK.IO using the UI or API.

[](/mkio/how-to/managing-edge-devices/on-board-fleet-devices/troubleshooting)

### Troubleshooting

How to troubleshoot common issues when on-boarding edge devices.

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