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

# Contacting Ledger support

How to contact Ledger support for Ledger Enterprise: the support portal, how to get access to it, and what to include in a support request.

This page tells you where to send a support request to Ledger, and what to include in it.

**Role: everyone.** Any user who has access to the support portal can open a support request.

## The support portal

Ledger support works through the **Ledger Enterprise support portal**:

<https://ledgerhq.atlassian.net/servicedesk/customer/portal/2>

Open one support request in the portal for each question or incident. Ledger support answers in that support request.

## If you do not have access

Access to the portal is by invitation. If you cannot sign in, ask your Technical Account Manager (TAM) at Ledger to send you an invitation by email.

## What to include

* **For an error on screen:** the error report. Select **Copy error report** on the error screen, then paste the report into your support request. See [**Error reports for Support**](/help-center-v2/reference/statuses-and-errors.md#error-reports-for-support).
* **For a Request:** the Request ID. In **Requests**, open the actions menu (⋮) at the end of the Request’s row, then select **Copy ID**. Paste the ID into your support request.
* **For a report that fails:** the report's date range and parameters.
* **For anything else:** the Workspace name, the Account or user concerned, and what you expected to happen.

> **Important:** Never send a PIN, a recovery phrase or a shard of the master seed, in the portal or anywhere else. Ledger support never asks for them. See [**Security good practice**](/help-center-v2/concepts/security-good-practice.md#phishing-and-ledger-support).

## Support requests for specific needs

| Need                                        | See                                                                                                                    |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Order Ledger Stax devices                   | [**Ordering Ledger Stax devices**](/help-center-v2/start-here/get-started/your-device.md#ordering-ledger-stax-devices) |
| Make a warranty claim                       | [**One-year limited warranty**](/help-center-v2/reference/warranty.md)                                                 |
| Add Clear Signing for a contract            | [**Contract operations**](/help-center-v2/guides/transactions/contract-operations.md)                                  |
| Enable single sign-on (SSO) for a Workspace | [**Signing in and out**](/help-center-v2/start-here/get-started/signing-in.md)                                         |

## Related

* [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md)
* [**Your security device**](/help-center-v2/start-here/get-started/your-device.md)
* [**Security good practice**](/help-center-v2/concepts/security-good-practice.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/contacting-support.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.