Business Accounts are in early access. We are working with design partners. Talk to us if you would like to build with them. When to use one
The model
A business account owns wallets. Access splits into two independent groups.
Members administer the account:
- Owner. Full control, including transferring ownership. Exactly one per account.
- Admin. Adds and removes members and signers, and links wallets.
- Viewer. Read-only access.
Signers approve transactions and messages for a specific wallet. Removing a signer revokes only that person’s ability to sign. The wallet and the other signers are unaffected.
The two are independent. Being an admin does not let someone sign, and being a signer does not grant admin rights.
Policies
Members and signers decide who can act. Policies decide what they’re allowed to do: rules that require extra approvals, cap amounts, or restrict destinations, layered from the environment down to a single signer.
See Policy Engine for the general model. Business accounts add one more layer on top, covered in Policies for the JavaScript SDK.
How it relates to embedded wallets
A business-account wallet is a Dynamic embedded wallet. What differs is ownership and access: the wallet belongs to the account rather than to one user, and you grant access by adding signers.
Everything in Embedded Wallets still applies, including the MPC architecture, key shares, and recovery. Once you are a signer, signing works the same way as for any embedded wallet.
Next steps
Pick your SDK under Implement in the sidebar. Each one covers the same path: create an account, add wallets, manage signers, administer members and roles, then sign.
