> ## Documentation Index
> Fetch the complete documentation index at: https://docs.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/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 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, and the user stays a signer so they keep final approval.                 |

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

<Warning>
  The two are independent. Being an admin does not let someone sign, and being a signer does not grant admin rights.
</Warning>

## 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](/docs/embedded-wallets/mpc/policies/overview) for the general model. Business accounts add one more layer on top, covered in [Policies](/docs/javascript/reference/business-accounts/policies/overview) 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](/docs/embedded-wallets/overview) 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.