> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/devices.md). # Devices Use **Devices** to onboard, register, organize, and monitor devices in Device Management. Use it as the starting point for the main device workflows. ### Before you start Before you onboard or register a device, confirm that: * your role includes permission to add or manage devices * the device can reach the Device Management server * the device belongs to the correct tenant, hierarchy, or group context Prepare these device details when available: * serial number * device ID * model * network or deployment context needed for placement and registration ### Device workflow Device setup usually follows this flow: 1. **Onboard** the device record in Device Management. 2. **Register** the device when it first contacts the server. 3. **View and manage** the device after it becomes active. 4. **Organize** the device by hierarchy or group. 5. **Monitor** device health, history, and lifecycle details. ### Understand the setup flow #### Onboarding Onboarding adds the device record to Device Management. Use it when you need to: * add one device manually * import many devices in one batch * prepare devices before first contact with the server Start with [Onboard a device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md). Then use: * [Add devices](/verifone-central-device-management/verifone-central/devices/add-devices.md) * [Add a single device](/verifone-central-device-management/verifone-central/devices/add-devices/add-a-single-device.md) * [Bulk import devices](/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md) #### Registration Registration happens when the device connects to the server for the first time. During registration, the platform exchanges device details and establishes the device in the estate. A successful registration moves the device into an active state. {% hint style="warning" %} If a device does not register, check that it was onboarded correctly, can reach the server, and is assigned to the expected network or hierarchy context. Then review [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) and [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md). {% endhint %} See: * [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) * [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md) * [Device life cycle](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-life-cycle.md) ### Common device tasks #### View and manage devices Use the device list to search for devices and perform common actions. * clone a device * delete a device * export device data * change device status * assign devices to groups * move devices between hierarchies Use: * [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) * [Device details](/verifone-central-device-management/verifone-central/devices/view-devices/device-details.md) #### Organize devices Use hierarchies and groups to control ownership, visibility, and bulk management. * [Manage hierarchies and groups](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups.md) * [Hierarchies](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups/hierarchies.md) * [Manage groups](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups/manage-groups.md) #### Monitor device health and lifecycle Use device health, tracking, and activity views to understand current state and recent issues. * [Active lifecycle and key indicators](/verifone-central-device-management/verifone-central/devices/active-lifecycle-and-key-indicators.md) * [Alerts and notifications](/verifone-central-device-management/verifone-central/devices/alerts-and-notifications.md) ### Next steps * Use [Onboard a device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md) to choose an onboarding method. * Use [Add devices](/verifone-central-device-management/verifone-central/devices/add-devices.md) to add one device or many devices. * Use [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) to search, filter, and manage existing devices. * Use [Device details](/verifone-central-device-management/verifone-central/devices/view-devices/device-details.md) to inspect one device in detail. * Use [Active lifecycle and key indicators](/verifone-central-device-management/verifone-central/devices/active-lifecycle-and-key-indicators.md) to review health, sync, and tracking data. ### Result After onboarding and registration, devices can be searched, organized, monitored, and managed from Device Management. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.verifone.com/verifone-central-device-management/verifone-central/devices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.