> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Quorum (multi-approval) Signer
> How an m-of-n quorum signer requires several members to approve a wallet action
A **quorum signer** has several member signers. A threshold of them must approve each transaction — for example, any 2 of 3 company officers. With a threshold of at least 2, one lost or stolen member key cannot move funds or change the wallet's signers on its own.
Quorum signers are available on EVM, Solana, and Stellar.
## How a Quorum Works
A quorum has three parts:
* **Members** — regular signers, such as email, phone, external wallet, server, or passkey signers.
* **Threshold** — the number of members that must sign, from 1 to the number of members.
* **Locator** — a `quorum:` identifier that Crossmint assigns when you add the quorum. You use it wherever the API takes a signer locator.
The quorum is the signer that acts. Its members only approve: each member signs its own approval message and submits it under its own locator. When the last required member signs, the transaction executes.
## Where You Can Use a Quorum
A quorum can fill any slot that a single signer can fill.
| Use | Example | Effect |
| - | - | - |
| Recovery method | The only recovery method is a 2-of-3 quorum | Recovery and signer changes need 2 members. One stolen credential cannot take over the wallet. |
| Recovery method, next to other methods | A 2-of-3 quorum plus an independent server recovery method | The server method acts alone. The quorum is a second path that needs 2 members. |
| Operational signer | A treasury wallet whose operational signer is a 3-of-5 quorum | Every transaction needs 3 of the 5 members. |
For the difference between the two roles, see [Recovery Methods](/wallets/concepts/recovery) and [Signers](/wallets/concepts/signers).
## Approval Flow by Chain
The approval flow is the same on every chain, except for who can approve.
| Chain | Who can approve |
| - | - |
| EVM | Any `threshold` members. All members are listed as pending. |
| Solana | Only the members you name in `approvingMembers` when you create the transaction. You must name exactly `threshold` members. |
| Stellar | Any `threshold` members. All members are listed as pending. |
On Solana, each approval message includes the set of signing members, so you choose that set before the members sign. If one of the named members cannot sign, create the transaction again with a different set.
A transaction that waits for approvals does not stay open forever. On Stellar, all required members must sign within about 8 minutes. On EVM and Solana, the transaction stays open for longer, up to a maximum lifetime that Crossmint sets. If the transaction expires, create it again.
## Rules and Limits
| Rule | Value |
| - | - |
| Members | 2 to 10, no duplicates |
| Member types | `email`, `phone`, `external-wallet`, `server`, `passkey` (no `passkey` on Solana) |
| Threshold | 1 to the number of members, at most 10 (at most 6 on Solana) |
| Nested quorums | Not supported |
| Member roles | A member can be in more than one quorum on the same wallet, and can also be a standalone recovery method or operational signer on that wallet |
A member that is also a standalone signer can act alone through that entry. The quorum then does not protect against theft of that member's key.
A quorum's members and threshold cannot change. To rotate a member or change the threshold, add a new quorum and then remove the old one. The new quorum gets a new locator. A recovery method approves each change, like any signer change. If that recovery method is a quorum, `threshold` of its members approve. When the old quorum is removed, its members can no longer approve, and transactions that wait for the old quorum fail.
## See Also
Create a quorum and approve transactions with it
Understand how recovery methods restore access
Choose signers for day-to-day wallet actions