Business Accounts are in early access. Talk to us if you’d like to build with them.
DynamicSDK.instance.businessAccounts.
Prerequisites
DynamicSDKinitialized with your environment ID (see the quickstart)- An authenticated user, because account operations act on behalf of the signed-in user
- Business Accounts enabled for your environment
The model
A business account owns wallets. Access is configured at two levels, Members and Signers. Members administer the account:- Owner: full control, including transferring ownership. Exactly one per account.
- Admin: add and remove members and signers, and link wallets.
- Viewer: read-only access to the account.
Being an admin does not let someone sign, and being a signer does not grant admin rights. Grant each explicitly.
How it fits with embedded wallets
A business-account wallet is a Dynamic embedded wallet. The difference is ownership and access: it belongs to the account, and you add people as signers instead of tying it to one user. Once you are a signer, you sign transactions and messages the same way as with any embedded wallet.Who can call what
Every method acts on behalf of the signed-in user. Reads require membership, and mutations such as adding members or signers, linking wallets, and transferring ownership require the owner or admin role. A call made without the required role fails, so checkdetail.members for the caller’s role before you show those actions in your UI.
Next steps
Create an account
Create an account and read back its details.
Add wallets
Link a wallet to the account, or remove one.
Manage signers
Grant and revoke signing access.
Members and roles
Administer membership and transfer ownership.