> ## Documentation Index > Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt > Use this file to discover all available pages before exploring further. # Vaults, wallets & addresses > Manage vaults, create wallets, and generate deposit addresses. export const ImageCarousel = ({images, perView = 3, children}) => { const [page, setPage] = useState(0); const [imgH, setImgH] = useState(0); const stripRef = useRef(null); const THUMB_MAX_WIDTH = 220; const PEEK_WIDTH = 34; useEffect(() => { const strip = stripRef.current; if (!strip) return; const measure = () => { const box = strip.querySelector("[data-carousel-imgbox]"); if (box && box.clientHeight) setImgH(box.clientHeight); }; measure(); const ro = new ResizeObserver(measure); ro.observe(strip); return () => ro.disconnect(); }, []); const fromChildren = React.Children.toArray(children).map(c => c && c.props && c.props.src ? { src: c.props.src, alt: c.props.alt } : null).filter(Boolean); const items = fromChildren.length ? fromChildren : images || []; if (!items.length) return null; const count = items.length; const columns = Math.min(perView, count); const totalPages = Math.ceil(count / columns); const showControls = totalPages > 1; const goTo = p => setPage((p % totalPages + totalPages) % totalPages); const prev = () => goTo(page - 1); const next = () => goTo(page + 1); const start = page * columns; const visible = items.slice(start, start + columns); const prevPeek = start > 0 ? items[start - 1] : null; const nextPeek = start + columns < count ? items[start + columns] : null; const renderPeek = (img, side) => { if (!img) return null; const isLeft = side === "left"; return }
{renderPeek(prevPeek, "left")} {} {Array.from({ length: columns }).map((_, i) => { const img = visible[i]; const slotStyle = { margin: 0, flex: "1 1 0", maxWidth: THUMB_MAX_WIDTH + "px", minWidth: 0 }; if (!img) { return {showControls && }
{showControls &&
{start + 1} {visible.length > 1 ? "–" + (start + visible.length) : ""} of {count}
} ; }; ## Overview Assets on the platform are organized in a four-level hierarchy: **organization → vaults → wallets → addresses**. Your organization is at the top — it holds your users, policies, and all vaults beneath it. Your institution's account. It owns all users, policies, and vaults, and defines who can do what across the platform. Multi-asset containers with customizable policies, quorums, and user permissions. Each vault operates independently with its own approval rules. Inside a vault, each asset is stored within a wallet. Multiple wallets of the same asset can exist within a vault — useful for segregating assets by counterparty. Each wallet can have one or more addresses. For UTXO networks like Bitcoin, multiple addresses can be created — all pooled to the same wallet. For account-based networks like Ethereum, the wallet address is unique. ### Structuring vaults by client or strategy To keep each client or strategy separate, create a dedicated vault for it—see [Creating vaults](/knowledge-base/platform/users/creating-vaults). Wallets created in that vault get their own deposit addresses, so funds stay segregated and addresses aren't accidentally reused across clients. When you create a wallet, you also control whether its address is shared with compatible networks. See [Wallet creation and management](/knowledge-base/platform/users/wallet-creation) for the address-sharing options. ## Managing vaults Administrators with vault management permissions may change vault settings. Changes are subject to quorum approval, after which Anchorage Digital will review the operation. ### Updating vault details To update a vault's name or description, tap the vault you want to adjust, then tap the **settings icon** in the upper right corner. Tap **Edit**, update the vault name and description as necessary, and tap **Save**. Updating vault details (name and description) does not require biometric approval. Vault settings screen with Edit highlighted Edit vault details screen with name and description fields ### Managing vault users Administrators with vault management permissions may add, edit user privileges, or remove users from vaults. #### Adding users to a vault To grant a user the ability to operate within a vault, add them and assign the appropriate permissions. In the iOS app, tap the desired vault, then tap the **settings icon** in the upper right corner and select the **Users** section. Tap **Add user** and select the user or users to add. To add all users, tap **Select all** and then **Continue**. Adjust user privileges by selecting a user and changing their permissions from **Initiate and approve** to **Initiate only** as needed, then select **Save changes**. Once all privilege changes are made, select **Done**. After reviewing the operation, submit biometric approval. Quorum approval is then required. Vault settings screen with Users highlighted Vault users list showing each user's initiate and approve permissions #### Changing vault user privileges To modify what actions a user is allowed to perform within a vault: In the vault settings menu, tap **Users**. Select a user and modify their privileges to either **Initiate and Approve** or **Initiate only**. After tapping **Finish and review**, the operation will go through quorum approval. Vault settings screen with Users highlighted Vault users list showing each user's initiate and approve permissions #### Removing users from a vault You can remove one or more users from a vault in a single operation. In the vault settings **Users** list, tap the **Select** option to choose the users you wish to remove. Select the users and follow the prompts to complete the removal process. Vault users list with the Select option in the top-right corner ### Deleting a vault Administrators with vault management permissions can delete vaults that are no longer in use. Once quorum is met, Anchorage Digital will review the operation before proceeding with deletion. In the vault settings menu, tap **Delete vault**. Add a comment (optional), then tap **Review** to review the operation. Once reviewed, submit it for approval. Vault settings screen with Delete vault highlighted ## Managing wallets ### Accessing wallet details From the wallet details page, you can: * Check wallet balances and holdings * Generate additional wallet addresses (if applicable) * Initiate withdrawals * Check the deposit address and pooled wallet addresses (if applicable) * Edit the wallet name **On iOS**: On the vault page, select the asset to see the associated wallets in the vault. Tap the wallet to see its details. **On web dashboard**: On the vault page, navigate to the **Wallet** tab and click on a wallet to see its details. Wallet details include balances, tokens associated with that address (e.g., ERC-20 tokens), staked balances, and other asset-specific information such as pooled addresses (BTC assets) or bank account information (USD wallets). Vault page showing the list of assets List of wallets for the selected asset Wallet detail screen with balance, deposit address, and pooled addresses ### Creating a new wallet Unlike creating a vault, creating a wallet in an existing vault doesn't require quorum approval. **On iOS**: Navigate to the desired vault and tap the asset you want to create additional wallets for. Tap the icon to create a new wallet and follow the prompts. Give the wallet a name and tap **Save** to create it. **On web dashboard**: Click **Create wallet** to begin. Select the network and click **Continue**. Give your wallet a name or use the default name, then select **Create wallet**. Your new wallet is ready for deposits and withdrawals and will appear in the table sorted by creation date. Create new wallet disclaimer screen ### Creating a new wallet address Additional addresses are available on UTXO-based networks (e.g., Bitcoin). All addresses are pooled to the same wallet. Tap the desired wallet, then tap **Deposit**. To view additional addresses, tap **Show all**, then **Generate new** to create a new address. Additional or pooled wallet addresses are only available on UTXO-based networks. Wallet detail screen with the Show all pooled addresses row ### One address per wallet on account-based networks On account-based networks like Ethereum, each wallet has a single address, and every token on that network shares it—ETH and all ERC-20 tokens in the wallet use the same deposit address. You can't add more addresses to the wallet itself; additional addresses are only available on UTXO-based networks, as described above. To get a separate deposit address on an account-based network, create another wallet in the vault—see [Creating a new wallet](#creating-a-new-wallet). ## Trusted destinations A **trusted destination** is an external address or bank recipient your organization has added to its allowlist of approved recipients. Adding a trusted destination requires quorum approval up front, before any funds move to it. Two approvals happen up front, each gated by quorum: **adding the trusted destination** to the allowlist, and **granting the transfer capability within the permission group** the API key belongs to. Both require quorum approval plus Anchorage Digital review. Once both are in place, the API key can transfer to its trusted destinations without collecting a separate quorum approval for each transaction. This is what makes trusted destinations practical for automated and high-frequency flows (treasury wallets, exchange accounts, settlement counterparties), while addresses outside the allowlist are not available to those API transfers. You can also configure a policy to only allow withdrawals to trusted destinations — turning the allowlist into a hard control rather than just a convenience. Today, two quorum-gated steps happen up front — adding the trusted destination, and granting the permission group's transfer capability; API transfers to trusted destinations then run without a separate per-transaction quorum. Applying a lower quorum to trusted-destination withdrawals is a planned Conditional Rules enhancement — see [Policies](/knowledge-base/platform/users/policies). ### Adding a trusted destination Administrators with trusted destination management permissions may add trusted destinations. Go to **Settings** and tap **Trusted destinations**, then tap **Add trusted destination**. Search for the asset, scan or paste the address, enter a name and description, then reply to the questionnaire. Submit biometric approval to initiate the operation. Once quorum is met, Anchorage Digital will review the operation. To use the same trusted destination across assets on the same network, select the checkbox under **Description**. It is also possible to add trusted destinations in the web dashboard. If initiated in the web dashboard, users are required to submit biometric approval in the iOS app. Trusted destinations list with Add trusted destination button Asset search screen for a new trusted destination New trusted destination form with address, name, and description fields New trusted destination form with the apply to all assets in network checkbox selected AML questionnaire for the new trusted destination Review screen for the new trusted destination before biometric approval ### Removing a trusted destination Only administrators with trusted destination management permissions can remove trusted destinations. Removal requires quorum and Anchorage Digital approval. Go to **Settings** and tap **Trusted destinations**. Tap the trusted destination to be removed. Review the details, tap **Remove**, and follow the prompts to submit biometric approval. Trusted destinations list Trusted destination detail screen with the Remove button