| Account | A holding of one asset on one network, governed by its own Rules or by a shared Policy |
| Administrator | A role that configures the Workspace: Accounts, Policies, Whitelists, groups, and users. Most governance changes need a Master Administrator. Administrators do not create or approve transactions |
| Allowance | The amount of a token that an ERC-20 approve call lets another address move from an Account's address |
| Any-asset Policy | A Policy which can apply to any asset. It cannot carry amount thresholds |
| API Administrator | An API user with the Administrator role. By default it has no permissions: the API admin rules of the Workspace define its access. An API Administrator cannot be a Master Administrator |
| API user | A user that holds its own key and approves over the API rather than on a Ledger device. It has the Administrator or the Operator role. A Master Administrator creates it from an externally generated public key, through a Request |
| Approval step | One stage in a Request's approval chain. Steps complete in order, and each has a quorum. In an Account Rule, a step names either one group or a list of Operators, never both |
| Approver | A user whose approval a Request requires. On Account Rules, Approvers are Operators. On Workspace governance Requests, they are Master Administrators. Under the API admin rules, they are API Administrators. The API calls an approval a review |
| APY | Annual percentage yield: the yearly reward rate the interface shows for a validator. It is shown before the validator's commission. Rates vary and Ledger does not guarantee them |
| Attested device | A Ledger Stax that Ledger attests for a Workspace. A user can restore their device from its 24-word recovery phrase onto an attested device. The device ID stays the same after the restore |
| Available balance | What an Account can send now. Lower than the total when pending Requests hold funds, or when the network keeps a minimum reserve |
| Baker | A validator on Tezos. Bakers produce blocks, receive the network's rewards, and pay a share to the Accounts that delegate to them |
| Connect | The section that links Accounts to dapps, through WalletConnect |
| Consolidate | On Ethereum staking, merging validators to reduce how many you run |
| Countervalue | An amount expressed in US dollars (USD) |
| Creator | The user who creates a Request. On an Account Rule, the Request initiator step sets who may create each operation: one group or a list of Operators. Creating the Request counts as the first approval |
| Cycle | On Tezos, a fixed number of blocks that the protocol uses as its unit of time, about one day |
| Derivation path | An Account's position in the key hierarchy, useful for reconciliation |
| Governance Rule | A statement of who may create an operation, within what amounts, to which destinations, and who must approve |
| Group | A named set of active Operators, usable in Account Rules instead of naming individuals. An approval step names either one group or a list of Operators, never both |
| Hardware Security Module (HSM) | The secure hardware holding your keys and enforcing your governance. It enforces Rules rather than interpreting them |
| Hosted Workspace | A Workspace whose HSM Ledger hosts. Its master seed comes from three Shared Owner devices |
| Initiator | The interface label for the Creator step of a Rule. See Creator |
| Key ceremony | The name that the Onboarding app gives to Workspace onboarding |
| Ledger device | The hardware that holds a user's PSD. It has its own screen, which displays what the user approves. The interface names it the Ledger Stax |
| Ledger Vault app | The app on the Ledger device that Ledger Enterprise uses for every device action, sign-in included. The interface calls it the Vault app. Its version must be exactly the version that the platform requires |
| Linked Accounts | Accounts on different EVM networks sharing an address at the same position in your key hierarchy. Separate Accounts, separate balances, separate governance |
| Master Administrator | An Administrator registered with a PSD. Master Administrators create and approve governance changes: Policies, Whitelists, groups, users, Account edits, and Workspace settings. They also manage Portfolios. The interface lists them as Master administrators. A Workspace starts with three, registered during Workspace onboarding |
| Master seed | The root of the keys of every Account in a hosted Workspace. The HSM generates it from three shards, one from each Shared Owner device. It never leaves the HSM |
| Matching Rule | The Rule a transaction falls under: the first Rule, in order, that matches the operation type, the amount, the recipient when the Rule has Whitelists, and the Creator. The send form names it once the amount and recipient are valid. It determines who must approve |
| Maximum fee | The fee ceiling authorized for a transaction. The network usually takes less; if it needs more, the transaction fails rather than costing more |
| Note | Optional free text on a Request, up to 1,000 characters in the interface, visible to Approvers |
| On-premises Workspace | A Workspace whose HSM runs on your organization's premises. It has no Shared Owners. Its onboarding registers an external signer |
| Onboarding app | The application that runs Workspace onboarding. It is separate from the Ledger Enterprise interface |
| Onboarding ID | The identifier that Ledger gives your organization for its Workspace onboarding. Each participant enters it in the Onboarding app |
| Operation | A single action on an Account: for example a transfer, a stake, a message signature |
| Operator | A role that creates and approves transactions and monitors Accounts. Operators read Policies, Whitelists, and the Rules of their Accounts, but cannot change them |
| Parent Account | An Account holding a network's native asset that pays the fees for the token Accounts attached to it |
| Partition | The part of the HSM that belongs to one Workspace. A Ledger device is connected to it at registration |
| Personal Security Device (PSD) | The credential that identifies a PSD user and signs their approvals. The PSD is held on the user's Ledger device, which displays what the user approves |
| Policy | A named, reusable set of governance Rules that Accounts adopt. Editing one changes every adopting Account |
| Portfolio | A grouping of Accounts. Operators linked as Read-only users can view its Accounts. It does not change approval Rules. A Master Administrator creates, edits, and deletes Portfolios directly, with no Request |
| Private Policy | The automatically named Rule set backing an Account that uses its own Rules. Not shown in the Policies list |
| Proof of control | A message signature that shows an auditor or a counterparty that you control an address |
| Quorum | The number of approvals an approval step requires |
| Recovery phrase | The 24 words that a Ledger device shows at setup. They restore the device on a Ledger Stax attested for the same Workspace |
| Recovery sheet | The paper on which a user writes the recovery phrase of their Ledger device. Every PSD user keeps one |
| Request | An action that moves assets, signs a message, or changes governance, users, or Accounts. It collects approvals, then executes. Some changes apply directly, with no Request: Portfolios, user suspension, reports, and API credential resets |
| Reveal | On Tezos, the operation that publishes an address's public key before its first outgoing operation |
| Shard | One of the three parts from which the HSM generates the master seed of a hosted Workspace. Each Shared Owner device gives one shard |
| Shared Owner | One of the three people who hold a shard of the master seed of a hosted Workspace. A Shared Owner keeps a Ledger device and its 24-word recovery phrase. A Shared Owner is not a Workspace user and does not sign in |
| Single-asset Policy | A Policy bound to one asset. Only this kind can carry amount thresholds |
| Single sign-on (SSO) | Sign-in through your organization's identity provider. Ledger support enables it for a Workspace. Each SSO identity is paired one time with one PSD user |
| Slashing | A protocol penalty that removes part of a validator's stake when the validator breaks the network's rules |
| Smart Contract Whitelist | A Whitelist of contract addresses. A Contract Interaction Rule uses it to limit which contracts an Account can call |
| Staking position | An amount delegated to one validator, with its own rewards and status |
| Technical Account Manager (TAM) | Your organization's named contact at Ledger. The TAM gives access to the support portal and advises on the custody of the master seed shards |
| Testnet | A copy of a network that exists for tests. Its assets have no market value |
| Threshold | The minimum, maximum, or range of amounts a Rule covers |
| Token Account | An Account holding a token, attached to a parent Account that pays its fees |
| Unspent output (UTXO) | On Bitcoin and similar networks, one previously received amount that has not yet been spent |
| Validator | A network participant you delegate to when staking. It keeps a commission on the rewards. The APY shown for a validator is before this commission, so the rate you receive is lower |
| WebHID | The browser interface through which the Ledger Enterprise interface and the update page reach the Ledger device over USB |
| Whitelist | A named, governed list of permitted destination addresses, referenced by Policy Rules |
| Withdraw | On Ethereum staking, the action that exits stake. It opens a page titled Unstake. Sui and Hedera call this action Unstake. Tezos calls it Undelegate |
| Workspace | Your organization's environment: its Accounts, people, governance, and history |
| Workspace onboarding | The key ceremony that creates a Workspace. It registers the first three Master Administrators, with a quorum of 2. For a hosted Workspace, it also generates the master seed |