> ## Documentation Index
> Fetch the complete documentation index at: https://www.dynamic.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Accounts

> Share embedded wallets across a team, with separate control over who manages the account and who can sign.

<Note>
  **Business Accounts are in early access.** We are working with design partners. [Talk to us](https://www.dynamic.xyz/talk-to-us) if you would like to build with them.
</Note>

A **business account** lets a team share [embedded wallets](/docs/embedded-wallets/mpc/overview) instead of tying each wallet to one person. A company treasury and an org-owned wallet are both business accounts. On top of shared ownership it adds flexible administration: you decide who can manage the account and who can sign, independently of each other.

## When to use one

| Use case | Shape |
| - | - |
| **Company treasury** | Shared wallets for operating funds. Teammates sign across them, and a server signer (coming soon) handles routine automated moves. |
| **Platform for business customers** | Provision wallets for other companies. Administer each customer's account without signing by default. |
| **Supervised consumer accounts** | A guardian administers the account while the end user signs day to day. |
| **User wallets with an agent** | An automated agent acts as a server signer (coming soon), and the user stays a signer so they keep final approval. |

## Ownership

A signed-in user creates the account and becomes its **owner**. Each account has exactly one owner, and the owner has full control, including the ability to transfer ownership to another member. Ownership transfer promotes an existing member to owner and demotes the previous owner to `admin` in the same step, so an account never has zero owners or two.

## What an account contains

Everything else hangs off the account, and the parts build on each other in this order.

| Part | What it is |
| - | - |
| [Members](/docs/business-accounts/members-and-roles) | The people who administer the account, each holding a role. |
| [Wallets and signers](/docs/business-accounts/wallets-and-signers) | Embedded wallets the account owns, and the members who can sign with each one. |
| [Governance](/docs/business-accounts/governance) | Approvals required before an account change applies. |
| [Policies](/docs/business-accounts/policies) and [quorum policies](/docs/business-accounts/quorum-policies) | Rules that limit what a wallet can sign and require approvals before it signs. |
| [Step up](/docs/business-accounts/step-up-auth) | The extra verification that sensitive account actions require. |
| [Webhooks](/docs/business-accounts/webhooks/account-actions) | Events for account changes and for [approval proposals](/docs/business-accounts/webhooks/proposals). |

<Warning>
  Members and signers are independent. Being an admin does not let someone sign, and being a signer does not grant admin rights. Grant each explicitly.
</Warning>

## Account details

An account has a name and other details that can change over time. A change to those details emits the `businessAccount.updated` event described in [Account action webhooks](/docs/business-accounts/webhooks/account-actions).

## 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.