# Key terms

A quick reference for terms that appear throughout this section.

* **Administrator.** A role that sets up accounts and defines the rules that govern them. See [For Administrators](/helpcenter2/overview.md).
* **Approval step.** A stage in an account's rules that requires a set number of approvals from named users or groups. A request can require several steps in sequence. See [Governance rules & whitelists](/helpcenter2/governance-rules-and-whitelists.md).
* **Available balance.** The portion of an account's balance you can transact with right now, as opposed to pending or staked amounts.
* **Blocking reason.** A condition that prevents a transaction from being created until it's resolved, shown as a message in the send flow.
* **Broadcast.** Sending a fully approved transaction out to the blockchain network.
* **Countervalue.** The value of a crypto amount expressed in fiat currency. Balances and amounts are shown in both the asset and its countervalue.
* **Creator.** A user or group permitted by an account's rules to initiate a request, such as a send.
* **Derivation path.** The technical path that identifies an account's address within the underlying wallet structure. Shown on the account's detail view.
* **Governance rules (rules).** The controls on an account that decide who can initiate transactions, where funds may go, and who must approve them. See [Governance rules & whitelists](/helpcenter2/governance-rules-and-whitelists.md).
* **HTS token.** A token issued through the Hedera Token Service. See [Hedera](/helpcenter2/network-specific-guidance/hedera-hbar-and-hts-tokens.md).
* **Mempool.** The pool of broadcast-but-not-yet-confirmed transactions on a network. A transaction still in the mempool can sometimes be replaced. See [Bitcoin: Replace by Fee](/helpcenter2/network-specific-guidance/bitcoin-replace-by-fee.md).
* **Operator.** A role that runs day-to-day operations: finding accounts, sending, receiving, and staking. See [For Operators](/helpcenter2/for-operators/operators-overview.md).
* **Physical Security Device (PSD).** The Ledger hardware device on which you review and authorise requests and verify receive addresses, so details are confirmed on trusted hardware.
* **Quorum (admin quorum).** The group of Administrators whose approval is required for administrative requests, such as creating or editing an account.
* **Request.** An action (send, stake, account creation, or account edit) that must pass an account's rules and be approved before it takes effect. See [How requests and approvals work](/helpcenter2/getting-started/how-requests-and-approvals-work.md).
* **Ruleset.** A named set of rules of one type on an account, for example send rules or a staking ruleset.
* **Side sheet.** The panel that opens alongside a list to show the details of a selected item, such as a request.
* **Spam.** A zero-amount transaction, hidden from the operations list by default. See [Operations, history & statuses](/helpcenter2/for-operators/operations-history-and-statuses.md).
* **SPL token.** A token issued on Solana. SPL token accounts attach to a parent Solana account. See [Solana: SPL token accounts](/helpcenter2/network-specific-guidance/solana-spl-token-accounts.md).
* **Staking position.** An amount delegated to a validator or provider to earn rewards. See [Staking](/helpcenter2/for-operators/staking.md).
* **Threshold.** A minimum and/or maximum amount set in an account's send rules.
* **Token account (parent / child).** A token account organised under a parent account on the same network, for example an HTS token account under an HBAR account, or an SPL token account under a Solana account.
* **Token association (Hedera).** A one-time link that lets a Hedera account hold a given token. An account can't receive a token it isn't associated with. See [Hedera](/helpcenter2/network-specific-guidance/hedera-hbar-and-hts-tokens.md).
* **Validator / provider.** The network node or staking partner to which staked funds are delegated. See [Staking](/helpcenter2/for-operators/staking.md).
* **Whitelist.** A named list of approved recipient addresses that can be attached to an account's send rules. See [Governance rules & whitelists](/helpcenter2/governance-rules-and-whitelists.md).


---

# Agent Instructions: 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:

```
GET https://help.enterprise.ledger.com/helpcenter2/getting-started/key-terms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.