> 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/registering.md).

# Registering as a new user

How an invited PSD user completes registration on Ledger Enterprise with the registration link and a Ledger device, before the first sign-in.

This page describes how you complete your registration after a Master Administrator invites you.

**Role: the invited PSD user.** The registration link opens a public page. It needs no sign-in.

## Before you start

* The **registration link** that a Master Administrator sent you.
* The Ledger device whose device ID you gave to that Master Administrator. See [**Your security device**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md).

## Complete your registration

1. Open the registration link. The page opens on **Welcome**, followed by your name.
2. Check the **Workspace**, the **Role** and the **Device ID**. The device ID must match the one that the Ledger Vault app shows.
3. Connect your Ledger device, and unlock it.
4. Select **Complete on Ledger device**.
5. Confirm the registration on your Ledger device.

The page then shows **Registration complete**. The **Status** becomes **Pending Administrator activation**. You cannot sign in yet. A Master Administrator must activate your user, and Master Administrators must approve the activation Request, up to the Confirmation Threshold.

When the activation Request is approved, the same link shows the status **Activated** and a **Sign in** button. Select **Sign in** to sign in with the registered Ledger device. See [**Signing in and out**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/signing-in.md).

**Complete on Ledger device** is available only in the statuses **Invitation created** and **Pending registration**.

## What can go wrong

* The platform accepts only the invited Ledger device. A device with another device ID cannot complete the registration.
* **Device paired with another workspace**: the Ledger device has a pairing record for another Workspace. Reinstall the Ledger Vault app on the device. Then select **Retry**. If the message shows again, contact Ledger support. See [**Your device and the Workspace partition**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md#your-device-and-the-workspace-partition).
* If a Master Administrator deletes the invitation, the link stops working.

## Related

* [**Signing in and out**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/signing-in.md)
* [**Your security device**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md)
* [**Users**](https://help.enterprise.ledger.com/help-center-v2/administration/users.md)


---

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