# Governance rules and whitelists An account's rules decide who can initiate transactions, where funds may go, and who must approve them. You set these up when [creating or editing an account](/helpcenter2/creating-and-editing-accounts.md). This page explains each building block. ## Send rules Send rules govern outgoing transactions. An account can have **up to four** sets of send rules, letting you apply different controls to different situations. Each set is built from: * **Creators** *(required)*: the users and/or groups allowed to initiate a send. Users and groups are clearly distinguished, and you can add, remove, and edit your selection. * **Whitelist** *(optional)*: restricts recipients to approved addresses (see below). * **Threshold** *(optional)*: a minimum and/or maximum amount, entered in the crypto asset, with the fiat countervalue shown. You can set just a minimum, just a maximum, or both; you can't save a set where the minimum exceeds the maximum. * **Approvers** *(optional)*: one or more approval steps. Each step is a set of users and/or groups plus the number of approvals required. You can require up to as many approvals as there are eligible approvers; a group counts as a **single approval** even if it appears in more than one selected group. Add multiple steps to require sequential approvals. > **Note:** Speed up repetitive setup. You can **duplicate** a set of send rules to pre-fill a new set, then tweak it, which is useful when several rule sets are mostly similar. Deleting the first rule set clears its entries but keeps the set available to fill again; additional sets can be removed entirely. ## Whitelists A whitelist is a named list of approved recipient addresses. When you attach one to a send rule, that rule can only send to addresses on the list. While building a rule you can see all active whitelists, search them by **name or address**, and see **how many addresses in each whitelist are compatible** with the account's asset. You can attach **multiple** whitelists to one account, and you can attach a whitelist that currently has no compatible address (you'll be told when none is available). > **Note:** For tokens, whitelisting is generally handled at the underlying network level. For example, Solana SPL token recipients are whitelisted via the Solana account. See [Solana: SPL token accounts](/helpcenter2/network-specific-guidance/solana-spl-token-accounts.md). ## Other rule types Some assets support additional rule types beyond sending. The most common is a **staking ruleset**, which controls who can initiate and approve staking. To save effort, you can **copy the content of your send rules** into an optional rule set; fields that fit are filled and the rest are dropped. * On **Ethereum**, the staking ruleset is limited to multi-authorization and threshold rules, and an Operator must be part of it to access staking. See [Ethereum: staking & Replace by Nonce](/helpcenter2/network-specific-guidance/ethereum-staking-and-replace-by-nonce.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/governance-rules-and-whitelists.md?ask= ``` 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.