Business Accounts are in early access. See Business Accounts for the model.
Wallets
An account gets a wallet in one of two ways. You can create a fresh wallet that the account owns from the start, or you can link an embedded wallet you already own so the team can share it. In both cases you become the wallet’s first signer. A wallet can belong to only one business account, and only the wallet’s owner can link it. An account can hold up to 10 wallets by default. See Limits for the configurable caps. Linking and removing a wallet are sensitive account actions, so they require step-up authentication and can be covered by approvals.Signers
A signer approves transactions and messages with a specific wallet. Adding a signer grants that member access to the wallet, and removing a signer revokes only their access, so the wallet and the other signers are unaffected. Only an owner or admin who is already an active signer on the wallet can add signers. A signer is not the same as an approver in an approval requirement. An approver signs off on a proposed action before it proceeds but holds no signing power, so a member with theviewer role can be a required approver. A signer is the only party that can produce the wallet’s signatures.
A wallet must always keep at least one active signer, because no one could approve anything afterward. Removing the last active signer is rejected, so add another signer or remove the wallet first. A wallet can have up to 10 signers by default; see Limits.
Server signers, which let an automated process sign without a person present, are coming soon. Only end-user signers are supported today.