> 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/getting-started.md). # Getting started Get started with Device Management from Verifone Central, including core areas, workflow, and key first steps. Manage payment devices across your estate from one place. Use Device Management to onboard, organize, monitor, and update devices. It also supports reporting and access control. Use this page to choose your first workflow. It is for administrators and operations teams. Watch this overview for a quick product tour. {% embed url="" %} ### Start with your goal Choose one goal before you begin: * **Set up or manage devices** — open [Devices](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices). * **Deploy a change** — open [Rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts). * **Investigate estate activity** — open [Dashboard](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/dashboard) or [Reports](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/reports). ### Before you start Confirm your role includes the required action. Also confirm your tenant, hierarchy, or group context. If an expected action is unavailable, review [User roles and permissions](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/user-roles-and-permissions) before changing your workflow. ### Capabilities Use Device Management to: * onboard and register devices * monitor health, lifecycle, and alerts * organize devices by tenant, hierarchy, and group * deploy software, parameters, and content ### 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](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/onboard-a-device) — choose how a device enters the estate * [Registering the device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/registering-the-device) — understand first contact with the server * [Active lifecycle and key indicators](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/active-lifecycle-and-key-indicators) — review device health, history, and custody progress * [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts) — review rollout progress across the estate ### Verify where to go next After you choose a workflow, confirm that: * you know which product area matches your task * you have the required access and context * you can name the next action and its expected result ### Result Start with the workflow that matches your goal. You can now choose the next action without guessing. ### Next steps * [Dashboard](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/dashboard) — review estate status and alerts * [Devices](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices) — start the main device workflow * [Rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts) — deploy changes across devices --- # 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/getting-started.md?ask=&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.