> Source: [/docs/accounts/use-cases](https://tempo.xyz/developers/docs/accounts/use-cases.md) > Section: [Accounts](https://tempo.xyz/developers/docs/accounts.md). Create accounts, set up signing methods, policies, access keys, key rotation, and fees, and follow guides for users, automations, agents, and teams. > [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md) > Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation. > If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly. # Use Cases Find the setup and guides for what you're building. ## Overview Each use case is a Tempo account setup for one kind of product. The setups differ in who holds which key. A customer holds a passkey, and a provider holds its own key. Your backend holds an access key, and each approver holds a signer. ## Apps For consumer apps, such as remittance or savings apps, built on embedded wallets from Privy, Turnkey, or a similar provider. [Set Up a Self-Custodial Wallet With a Provider](https://tempo.xyz/developers/docs/accounts/apps/self-custodial-wallets): The provider's key and the user's passkey approve together; the user can recover or leave without you. Devnet until T14. [Recover a User's Account](https://tempo.xyz/developers/docs/accounts/apps/recover-an-account): Replace a lost passkey with the signers the user still has. Devnet until T14. ## Automations For backends that pay out, fund cards, or charge subscriptions, and for AI agents that pay on someone's behalf. Each gets its own access key. [Pay Out From a Backend](https://tempo.xyz/developers/docs/accounts/automations/pay-out-from-a-backend): Pay approved payees up to a daily limit with a key in your KMS. [Pay From a User's Embedded Wallet](https://tempo.xyz/developers/docs/accounts/automations/pay-from-an-embedded-wallet): Have a user's Privy or Turnkey wallet authorize a key once, so your backend pays within limits. [Give an Agent a Wallet](https://tempo.xyz/developers/docs/accounts/automations/give-an-agent-a-wallet): An agent's own key, with a budget, an expiry, and only the calls it needs. ## Custodians For exchanges and payments processors that hold customer funds. Also for businesses whose funds sit with a custodian such as Fireblocks, and companies running their own treasury. [Hold Customer Funds in an Omnibus Account](https://tempo.xyz/developers/docs/accounts/custodians/omnibus-accounts): A deposit address per customer, paying into one account that accepts only the stablecoins you list. [Custody Partners](https://tempo.xyz/developers/docs/partners/wallets#custodial--institutional): Custodians and institutional wallets that support Tempo, such as Fireblocks. [Set Up a Team Multisig](https://tempo.xyz/developers/docs/accounts/custodians/team-multisig): Three approvers, any two of whom approve each payment. Devnet until T14. ## Wallets For wallet teams adding Tempo, such as MetaMask, Rabby, or Ledger, and for apps whose users connect those wallets. [Add Tempo to Your Wallet](https://tempo.xyz/developers/docs/accounts/wallets/add-tempo-to-your-wallet): Add the networks, show stablecoin balances, let users pay fees in stablecoins, and send Tempo Transactions. ## Related [Apps](https://tempo.xyz/developers/docs/accounts/apps): Covers how each user's account is set up with your wallet provider, and who can move the funds. [Automations](https://tempo.xyz/developers/docs/accounts/automations): Covers giving each service or agent its own access key with a limit, scopes, and an expiry. [Custodians](https://tempo.xyz/developers/docs/accounts/custodians): Covers the recommended setup for omnibus accounts, custodian-held funds, and company treasuries. [Wallets](https://tempo.xyz/developers/docs/accounts/wallets): Covers connecting MetaMask, Rabby, or Tempo Wallet to your app, and what a single-key account can do.