> 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/readme.md). # Ledger Enterprise Help Center Guides, reference material, and concepts for operating your digital assets on Ledger Enterprise. *** Ledger Enterprise gives your organization custody and control of digital assets under governance you define. **Every action that moves value or changes a Rule is enforced by hardware**, not by software you have to trust. This Help Center is organized around what you are trying to do. ## Where to go

Section	Use it when
Start here	You are new: the layout, your device, registration, signing in, or working through the API
Guides	You have a task to complete now
Administration	You configure governance, users or the Workspace
Concepts	You want to understand how governance and security actually work
Reference	You need a specific fact: a network's behavior, a status, a limit, a term

## How every task works Almost every task follows the same shape. You complete a form, approve it with your own key, and the action becomes a **Request** that others approve before it takes effect. The model is described in full in [**How governance works**](/help-center-v2/concepts/how-governance-works.md). ## Guides by area

Area	Covers
Accounts	Finding Accounts, reading balances, creating and editing Accounts
Transactions	Sending, receiving, reviewing history, signing messages, and contract operations
Staking	Delegating assets to receive network rewards
Requests and approvals	Approving, rejecting, and tracking Requests
Connect	Using dapps from an Account
Reports	Exporting transactions and balances. Requests reports are under development

## Administration by area

Area	Covers
Workspace onboarding	The onboarding ceremony, Shared Owners, and master seed recovery
Governance	Policies, Whitelists, Portfolios, and Workspace settings
Users	PSD and API users, registrations, API credentials, and groups

## Roles What you can do depends on your role, and each guide states the role a task needs. * **Administrators** configure the Workspace. They do not create or approve transactions. * **Master Administrators** are the Administrators registered with a Personal Security Device (PSD). They create and approve changes to Policies, Whitelists, groups, users and Workspace settings. They also manage Portfolios. An API Administrator cannot be a Master Administrator. * **Operators** create and approve transactions, and monitor Accounts. They can read Policies, Whitelists and the Rules of their Accounts, but cannot change them. The platform enforces this separation. It is not a convention, so an action you expect can be unavailable to you: see [**How governance works**](/help-center-v2/concepts/how-governance-works.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/readme.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.