> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md).

# Your security device

What your Ledger Enterprise security device does, when you need it, and how to handle it safely.

Your Personal Security Device (PSD) is the Ledger hardware that proves who you are and approves what you do. It is personal: it represents you inside your Workspace and is not shared.

## When you need it

| Action                                       | Device needed                              |
| -------------------------------------------- | ------------------------------------------ |
| Signing in                                   | Yes                                        |
| Creating any Request, such as a transfer     | Yes                                        |
| Approving someone else's Request             | Yes                                        |
| Verifying a deposit address                  | Yes, and this is the point of the exercise |
| Rejecting a Request                          | No                                         |
| Reading balances, history, Rules, or reports | No                                         |

Connect and unlock the device **before** starting a task rather than partway through.

## What it shows you

The device has its own screen, and what appears there is read from the secure hardware rather than from your browser. When you approve an operation, the recipient, the amount, and the operation type shown on the device are the ones that will actually execute.

**Read them there.** This is what makes the whole model work: see [**The security model**](/help-center-v2/concepts/the-security-model.md).

> **Important:** If the details on the device do not match your screen, reject on the device, do not retry, and contact support.

## Handling it safely

* **Keep it physically secure.** Someone holding your unlocked device can act as you, within your role and your approval rights.
* **Never share your PIN**, and never enter it anywhere other than on the device itself. Nobody at Ledger will ask for it.
* **Keep your recovery material offline and separate from the device.** Anyone with it can reconstruct your access.
* **Disconnect when you are done**, particularly on shared machines.

> **Warning:** Nobody legitimate will ever ask for your PIN or your recovery material, by email, chat, phone, or a web page. Any such Request is an attack, whatever it appears to come from.

## If something is wrong

<table><thead><tr><th width="293.859375">Situation</th><th>What to do</th></tr></thead><tbody><tr><td>The browser does not detect the device</td><td>Check it is connected and unlocked, then reload. Try another cable or port before concluding it has failed</td></tr><tr><td>You cannot remember your PIN</td><td>Contact your Administrator. Do not keep guessing</td></tr><tr><td>The device is lost or stolen</td><td>Tell your Administrator <strong>immediately</strong> so your access can be revoked</td></tr><tr><td>The device is damaged</td><td>Contact your Administrator to arrange a replacement and re-registration</td></tr></tbody></table>

Losing the device does not put your organization's assets at immediate risk, because approval quorums mean one device is rarely sufficient on its own. It still needs reporting at once.

## Related

* [**Orientation**](/help-center-v2/start-here/get-started.md)
* [**The security model**](/help-center-v2/concepts/the-security-model.md)
* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)

## Setting up your device for the first time

To be completed.

> **Editorial note (remove before publishing):** Cover the sequence for a new user: registration link, activation, PIN setup, and pairing with the Workspace. Also list the device models supported.


---

# 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://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.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.