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

# Orientation

What Ledger Enterprise does, how the interface is laid out, and what you need before your first task.

Ledger Enterprise is where your organization holds and moves digital assets under Rules it defines. You work in a **Workspace**: your Accounts, your people, your governance, your history.

## What you need

* **Your security device**, initialized and paired with your Workspace. See [**Your security device**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md).
* **A role.** Your role decides which sections you see and which actions you can take.

## The layout

Everything is reached from the left-hand navigation. Accounts and Requests are at the top. **Governance** holds Policies, Whitelists, Workspace and Portfolios. **User management** holds Users and Groups. **Tools** holds Reports and Connect. What you see depends on your role and on which capabilities your Workspace uses, so your list may be shorter than this.

<table><thead><tr><th width="162.09765625">Section</th><th width="421.578125">What it is for</th><th>Who sees it</th></tr></thead><tbody><tr><td><strong>Accounts</strong></td><td>Your holdings, balances, history, and per-Account Rules</td><td>Everyone</td></tr><tr><td><strong>Requests</strong></td><td>All Requests you have a view on. Everything awaiting approval, including what is waiting on you</td><td>Everyone</td></tr><tr><td><strong>Policies</strong></td><td>Reusable governance Rule sets that Accounts adopt</td><td>Master Administrators write, Administrators and Operators read</td></tr><tr><td><strong>Whitelists</strong></td><td>Governed lists of permitted destination addresses</td><td>Master Administrators write, Administrators and Operators read</td></tr><tr><td><strong>Workspace</strong></td><td>Workspace-level governance, certificates, and external signers</td><td>Administrators</td></tr><tr><td><strong>Portfolios</strong></td><td>Groupings of Accounts. Operators linked as <strong>Read-only users</strong> can view the Accounts of a Portfolio</td><td>Administrators read, Master Administrators manage</td></tr><tr><td><strong>Users</strong></td><td>People in the Workspace, and invitations to join</td><td>Administrators</td></tr><tr><td><strong>Groups</strong></td><td>Named sets of Operators, usable in Rules instead of naming individuals</td><td>Administrators</td></tr><tr><td><strong>Reports</strong></td><td>Exports of your activity</td><td>Everyone</td></tr><tr><td><strong>Connect</strong></td><td>Links your Accounts to dapps</td><td>Operators</td></tr></tbody></table>

> **Note:** If a section is missing, it is either not available to your role or not enabled for your Workspace. Your account manager can confirm which.

## Inside an Account

An Account opens on tabs. Which tabs appear depends on the asset and on your permissions on the Account:

<table><thead><tr><th width="192.7578125">Tab</th><th>Shows</th></tr></thead><tbody><tr><td><strong>Overview</strong></td><td>Balances and a summary</td></tr><tr><td><strong>Operations</strong></td><td>The full operation history</td></tr><tr><td><strong>UTXOs</strong></td><td>The individual unspent outputs, on Bitcoin and similar networks</td></tr><tr><td><strong>Token Accounts</strong></td><td>Token Accounts attached to this Account</td></tr><tr><td><strong>Linked Accounts</strong></td><td>The same address on other EVM networks</td></tr><tr><td><strong>Staking</strong></td><td>Positions and staking actions, where the asset supports it</td></tr><tr><td><strong>Messages</strong></td><td>Message signatures. The tab shows only when a Rule of the Account lets you sign messages</td></tr><tr><td><strong>Rules</strong></td><td>The governance Rules applying to this Account</td></tr><tr><td><strong>Account info</strong></td><td>Identity details, including the derivation path</td></tr></tbody></table>

## Notifications

While the interface is open, it shows pop-up notifications about events that concern you. A pop-up closes by itself after 5 to 12 seconds. The interface does not show a missed pop-up again. To find the Requests that wait for you, open [**Requests**](https://help.enterprise.ledger.com/help-center-v2/guides/requests.md).

Select a Request pop-up to open the Request. Select a user pop-up to open **Users**, and a report pop-up to open **Reports**.

| Pop-up                                                                          | When it shows                                                       | Who gets it                                                                                                                                                                           |
| ------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Approval required**                                                           | A Request reaches an approval step                                  | For a transaction or message signature Request, the Approvers of that step. For any other Request, every Administrator. Never the Creator                                             |
| **Request executed**                                                            | A Request received its approvals and was executed                   | For a transaction or message signature Request, the Creator and the Approvers. For any other Request, every Administrator                                                             |
| **Request rejected**                                                            | A Request was rejected                                              | For a transaction or message signature Request, the Creator and the Approvers of the steps reached so far. For any other Request, every Administrator. Never the user who rejected it |
| **Request failed**                                                              | A Request failed                                                    | For a transaction or message signature Request, the Creator and the Approvers of the steps reached so far. For any other Request, every Administrator                                 |
| **Operation confirmed**                                                         | A transaction was confirmed on-chain                                | Every user who can see the sending Account                                                                                                                                            |
| **Operation dropped**                                                           | A transaction no longer progresses on-chain                         | Every user who can see the sending Account                                                                                                                                            |
| **Operation failed**                                                            | The processing of a transaction failed                              | Every user who can see the sending Account                                                                                                                                            |
| **Admin user registration completed**, **Operator user registration completed** | An invited user completed the registration and waits for activation | Master Administrators                                                                                                                                                                 |
| **User suspended**, **User unsuspended**                                        | A user was suspended, or the suspension was lifted                  | Master Administrators                                                                                                                                                                 |
| **Report ready**, **Report failed**                                             | A report is ready to download, or could not be generated            | The user who generated the report                                                                                                                                                     |

## Your first tasks

1. [**Set up and understand your device**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md)
2. [**Complete your registration**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/registering.md) from the link that you received
3. [**Sign in**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/signing-in.md)
4. [**Read how governance works**](https://help.enterprise.ledger.com/help-center-v2/concepts/how-governance-works.md), which explains how approvals work
5. [**Find your Accounts and read their balances**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/finding-accounts-and-balances.md)
6. Then either [**send**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md) or [**receive**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/receiving-assets.md)

If you work through the API, start with [**API users**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/api-users.md).

If you are one of the first three Administrators of a new Workspace, or one of its Shared Owners, start with [**Workspace onboarding**](https://help.enterprise.ledger.com/help-center-v2/administration/onboarding.md). That key ceremony creates the Workspace, before anyone can sign in.

## Related

* [**Contacting Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md)
* [**Signing in and out**](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/signing-in.md)
* [**How governance works**](https://help.enterprise.ledger.com/help-center-v2/concepts/how-governance-works.md)
* [**The security model**](https://help.enterprise.ledger.com/help-center-v2/concepts/the-security-model.md)
* [**Workspace onboarding**](https://help.enterprise.ledger.com/help-center-v2/administration/onboarding.md)
* [**Glossary**](https://help.enterprise.ledger.com/help-center-v2/reference/glossary.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.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.
