> ## Documentation Index > Fetch the complete documentation index at: https://docs.privy.io/llms.txt > Use this file to discover all available pages before exploring further. # Organization wallets Privy powers programmable wallets for organizations, allowing multiple people to securely hold funds, manage access, and operate financial workflows together. Organizations can represent businesses, institutions, nonprofits, agencies, or any other group that shares ownership of funds and financial operations. They can define granular roles, permissions, and approval workflows to govern how funds move. Organization wallets support both custodial and non-custodial deployments. In non-custodial setups, neither Privy nor your application ever holds complete control of the wallet's private key. images/org-overview.png Read below to learn how developers use organization wallets to build payments platforms, business banking products, payroll systems, spend management tools, and more. ## Controls Privy's wallet abstraction allows you to assign granular permissions over organization wallets to specific individuals within the organization. Organizations are modeled via a [**root key quorum**](/organizations/setup/quorum) that by default owns and administrates all of the organization's wallets. The root key quorum can then [provision scoped wallet access](/organizations/setup/signers) to other members of the organization. Privy's ownership semantics also support arbitrary quorum-based approvals, enabling you to require any permutation and threshold of users in order to take sensitive actions. ## Asynchronous authorization With organizations, sensitive actions taken by wallets often require a quorum of approvals from users that may not all be online simultaneously. Privy's **intents** system support asynchronous authorization of wallet actions, streamlining the process of collecting approvals across a quorum of users. Simply create an intent to take an action (e.g. send a transaction) and have users approve asynchronously at their leisure. ## Policies Privy's [policy engine](/controls/policies/overview) supports enforcing granular rules on signing and transaction execution across any of Privy's [tier 3 chain types](/wallets/overview/chains). Organizations can configure guardrails including allowlisted and denylisted addresses, amount thresholds, allowed chains, and more. You can also assign specific policies to specific users or groups of users to [formalize access control within Privy's policy engine](/organizations/setup/signers). ## Payments Privy has native support for [fiat and crypto payins and payouts](/wallets/funding/overview). Organizations can fund wallets via bank deposits, cross-chain crypto deposits, card payments, and more. Organizations can execute payouts to fiat (across a variety of currencies) and crypto, with native support for swapping and bridging at fixed rates.