> 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/devices/sign-in.md).
# Sign in
Sign in to open **Device Management** and access the correct device estate.
### Before you sign in
Make sure you have:
* valid Device Management credentials
* access to the customer or estate you need to manage
* the account assigned to your required role and scope
Stop here if you do not know the customer or estate context. Confirm it with your administrator before signing in.
### Sign in
{% stepper %}
{% step %}
### 1. Open Device Management
Go to **Verifone Central** → **Device Management**.
{% endstep %}
{% step %}
### 2. Enter your credentials
Enter your username and password.
{% endstep %}
{% step %}
### 3. Complete sign-in
Select **Sign in**.
{% endstep %}
{% endstepper %}
### Verify your access
The **Dashboard** opens after a successful sign-in.
Check that the displayed customer or estate matches your intended scope. Then confirm that the action you need is available.
Do not manage devices or schedule rollouts in an unexpected customer or estate. Sign out and use the correct account instead.
### If sign-in fails
Use the message shown on the sign-in page to choose the next action:
* **Credentials rejected** — re-enter your username and password. Check that you are using the intended account.
* **Access unavailable** — confirm that your account has Device Management access for the needed customer or estate.
* **Access is still blocked** — contact your administrator. Share the account used, the customer or estate needed, and the displayed message.
### Result
You are ready to work when the **Dashboard** opens, the context is correct, and your required actions are available.
### Next steps
* [Dashboard](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/dashboard) — review KPIs, charts, and estate status
* [View devices](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/view-devices) — search for devices and manage device actions
* [Alerts and notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications) — review operational events and follow-up items
---
# 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/devices/sign-in.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.
