> 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-getting-started/verifone-central/verifone-central-device-manager/reports/device-management.md).

# Device management

Open chain of custody and device report pages from one report hub.

Open device-focused reports from **Reports** → **Device management**.

### When to use this page

Use this page when you need report output for devices instead of audit events.

Use it to choose between custody tracking and general device report data.

### Available reports

This section includes:

* [Chain of Custody report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/chain-of-custody-report) — track shipped devices and review custody records
* [Device report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/device-report) — view device-level report details

### Choose the right report

Use **Chain of Custody report** when you need movement, custodian, or location history.

Use **Device report** when you need a broader device record view and a device export.

Choose the report before downloading data. A device export is not a custody-history export.

### Open device management reports

{% stepper %}
{% step %}

### 1. Open Reports

Go to **Verifone Central** → **Device Management** → **Reports**.
{% endstep %}

{% step %}

### 2. Open Device management

Select **Device management**.
{% endstep %}

{% step %}

### 3. Select the report

Choose **Chain of Custody** or **Device Report**.
{% endstep %}
{% endstepper %}

### Verify the result

After you open a report, confirm that:

* the selected report matches the data you need
* the report page supports the action you plan to take
* you are on the correct page before you export or import data

### Before you change custody data

Use the Chain of Custody report to review the target records first.

Export the current scope before a bulk update. Keep it as the pre-change reference.

Stop if the displayed records include devices outside the intended update scope.

### Result

The selected report opens with the right data source for review or export.

### Next steps

* [Chain of Custody report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/chain-of-custody-report) — review custody data and related file actions
* [Device report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports/device-management/device-report) — review device data and export output


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/reports/device-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.