For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

You are new: the layout, your device, registration, signing in, or working through the API

You have a task to complete now

You configure governance, users or the Workspace

You want to understand how governance and security actually work

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.

Guides by area

Area
Covers

Finding Accounts, reading balances, creating and editing Accounts

Sending, receiving, reviewing history, signing messages, and contract operations

Delegating assets to receive network rewards

Approving, rejecting, and tracking Requests

Using dapps from an Account

Exporting transactions and balances. Requests reports are under development

Administration by area

Area
Covers

The onboarding ceremony, Shared Owners, and master seed recovery

Policies, Whitelists, Portfolios, and Workspace settings

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.

Last updated