> 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/reference/glossary.md).

# Glossary

The terms used across the Ledger Enterprise Help Center, in plain language.

<table><thead><tr><th width="172.30859375">Term</th><th>Meaning</th></tr></thead><tbody><tr><td>Account</td><td>A holding of one asset on one network, governed by its own Rules or by a shared Policy</td></tr><tr><td>Administrator</td><td>A role that configures the Workspace: Accounts, Policies, Whitelists, and users. Administrators do not create transactions</td></tr><tr><td>Any-asset Policy</td><td>A Policy which can apply to any asset. It cannot carry amount thresholds</td></tr><tr><td>API user</td><td>A user that holds its own key and approves over the API rather than on a Ledger device. An Administrator creates it from an externally generated public key</td></tr><tr><td>Approval step</td><td>One stage in a Request's approval chain. Steps complete in order, and each has a quorum</td></tr><tr><td>Available balance</td><td>What an Account can send right now. Lower than the total when funds are pending or staked</td></tr><tr><td>Baker</td><td>A validator on Tezos. Bakers produce blocks, receive the network's rewards, and pay a share to the Accounts that delegate to them</td></tr><tr><td>Connectivity Hub</td><td>The section used to reach external applications</td></tr><tr><td>Consolidate</td><td>On Ethereum staking, merging validators to reduce how many you run</td></tr><tr><td>Countervalue</td><td>An amount expressed in your Workspace's reporting currency</td></tr><tr><td>Creator</td><td>Someone permitted to create a given operation on a given Account, set per Rule</td></tr><tr><td>Derivation path</td><td>An Account's position in the key hierarchy, useful for reconciliation</td></tr><tr><td>Governance Rule</td><td>A statement of who may create an operation, within what amounts, to which destinations, and who must approve</td></tr><tr><td>Group</td><td>A named set of people, usable in Rules instead of naming individuals. Someone in several groups named in one step counts once</td></tr><tr><td>Hardware Security Module (HSM)</td><td>The secure hardware holding your keys and enforcing your governance. It enforces Rules rather than interpreting them</td></tr><tr><td>Linked Accounts</td><td>Accounts on different EVM networks sharing an address at the same position in your key hierarchy. Separate Accounts, separate balances, separate governance</td></tr><tr><td>Matching Rule</td><td>The Rule a transaction falls under, named in the send form once the amount &#x26; recipient are valid. It determines who must approve</td></tr><tr><td>Maximum fee</td><td>The fee ceiling authorized for a transaction. The network usually takes less; if it needs more, the transaction fails rather than costing more</td></tr><tr><td>Note</td><td>Optional free text on a Request, up to 1,000 characters in the interface, visible to Approvers</td></tr><tr><td>Operation</td><td>A single action on an Account: for example a transfer, a stake, a message signature</td></tr><tr><td>Operator</td><td>A role that creates transactions and monitors Accounts. Operators read governance configuration but cannot change it</td></tr><tr><td>Parent Account</td><td>An Account holding a network's native asset that pays the fees for the token Accounts attached to it</td></tr><tr><td>Personal Security Device (PSD)</td><td>The credential that identifies a user and signs their approvals. A PSD is normally held on a Ledger device, which displays what you approve and signs it</td></tr><tr><td>Policy</td><td>A named, reusable set of governance Rules that Accounts adopt. Editing one changes every adopting Account</td></tr><tr><td>Portfolio</td><td>A grouping of Accounts for organization and reporting. Read-only users can be linked to a Portfolio as well. It does not affect governance</td></tr><tr><td>Private Policy</td><td>The automatically named Rule set backing an Account that uses its own Rules. Not shown in the Policies list</td></tr><tr><td>Quorum</td><td>The number of approvals an approval step requires</td></tr><tr><td>Request</td><td>Any action that changes something. It collects approvals, then executes</td></tr><tr><td>Reviewer</td><td>Someone whose approval a Request requires. Also called an Approver</td></tr><tr><td>Single-asset Policy</td><td>A Policy bound to one asset. Only this kind can carry amount thresholds</td></tr><tr><td>Staking position</td><td>An amount delegated to one validator, with its own rewards and status</td></tr><tr><td>Threshold</td><td>The minimum, maximum, or range of amounts a Rule covers</td></tr><tr><td>Token Account</td><td>An Account holding a token, attached to a parent Account that pays its fees</td></tr><tr><td>Unspent output (UTXO)</td><td>On Bitcoin and similar networks, one previously received amount that has not yet been spent</td></tr><tr><td>Validator</td><td>A network participant you delegate to when staking. Its commission is deducted from the yield</td></tr><tr><td>Whitelist</td><td>A named, governed list of permitted destination addresses, referenced by Policy Rules</td></tr><tr><td>Withdraw</td><td>On Ethereum staking, the action that exits stake. Other networks call this Unstake</td></tr><tr><td>Workspace</td><td>Your organization's environment: its Accounts, people, governance, and history</td></tr></tbody></table>

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Limits**](/help-center-v2/reference/limits.md)
* [**Networks**](/help-center-v2/reference/networks.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.enterprise.ledger.com/help-center-v2/reference/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
