> 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/verifone-central-device-management-introduction.md).

# Verifone Central Device Management Introduction

Manage payment devices across your estate from one place.

Use Device Management to onboard, register, monitor, organize, and update devices. It also supports reporting and access control.

Watch this overview for a quick product tour.

{% embed url="<https://vimeo.com/1140505171/57b7df9063?fe=cm&fl=pl>" %}

### Before you start

Before you begin, confirm that:

* your role includes access to the features you need
* your tenant, hierarchy, or group context is correct
* you know whether you need device setup, rollout management, reporting, or administration

### Choose your starting point

Use this quick routing when you need the right first page:

* start with [Devices](/verifone-central-device-management/verifone-central/devices.md) when you need to onboard, register, or manage devices
* start with [Dashboard](/verifone-central-device-management/verifone-central/devices/dashboard.md) when you need estate status, alerts, or KPIs
* start with [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md) when you need to deploy software, parameters, or content
* start with [Reports](/verifone-central-device-management/verifone-central/reports.md) when you need audit, device, or custody output
* start with [User roles and permissions](/verifone-central-device-management/verifone-central/user-roles-and-permissions.md) when you need to confirm access scope

### What it helps you do

Use Device Management to:

* onboard and register devices
* monitor health, lifecycle, and alerts
* organize devices by tenant, hierarchy, and group
* schedule software, parameter, and content rollouts
* track assets through their lifecycle
* generate operational and audit reports
* control user access by role

### Core areas

Choose the area that matches your task:

* [Devices](/verifone-central-device-management/verifone-central/devices.md) — add, register, search, and manage devices
* [Asset tracking](/verifone-central-device-management/verifone-central/asset-tracking.md) — track device movement and lifecycle status
* [Tenants](/verifone-central-device-management/verifone-central/tenants.md) — manage customer or organizational boundaries
* [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md) — distribute software, parameters, and content
* [Reports](/verifone-central-device-management/verifone-central/reports.md) — review audit, operational, and device data
* [User roles and permissions](/verifone-central-device-management/verifone-central/user-roles-and-permissions.md) — understand role-based access

### Typical workflow

Most teams use Device Management in this order:

1. Add devices to the estate.
2. Register devices when they first connect.
3. Organize devices by tenant, hierarchy, or group.
4. Monitor health, alerts, and lifecycle status.
5. Roll out software, parameters, or content.
6. Review reports and audit data.

### Common first tasks

Use these pages for common first actions:

* [Onboard a Device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md) — choose how a device enters the estate
* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — understand first contact with the server
* [Active lifecycle and key indicators](/verifone-central-device-management/verifone-central/devices/active-lifecycle-and-key-indicators.md) — review device health, history, and custody progress
* [Monitor estate-wide rollouts](/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts.md) — review rollout progress across the estate
* [Chain of Custody report](/verifone-central-device-management/verifone-central/reports/device-management/chain-of-custody-report.md) — review shipped device custody data

### Verify where to go next

After you review this page, confirm that:

* you know which product area matches your task
* you know whether the next step is device work, rollout work, reporting, or administration
* you can open the right section without guessing

### Result

Start with **Devices**, **Dashboard**, or **User roles and permissions**, based on your task.

### Next steps

* [Dashboard](/verifone-central-device-management/verifone-central/devices/dashboard.md) — review estate status and alerts
* [Devices](/verifone-central-device-management/verifone-central/devices.md) — start the main device workflow
* [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md) — deploy changes across devices
* [Reports](/verifone-central-device-management/verifone-central/reports.md) — open reporting workflows


---

# 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/verifone-central-device-management-introduction.md?ask=<question>&goal=<endgoal>
```

`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.
