> ## 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're working with design
  partners — [talk to us](https://www.dynamic.xyz/talk-to-us) if you'd like
  to build with them.
</Note>

A **business account** lets a team share [embedded wallets](/docs/javascript/reference/waas/creating-waas-wallet-accounts) — for example a company treasury or an org-owned wallet — instead of tying each wallet to one person. On top of that, it adds flexible administration: you decide who can manage the account and who can sign, independently.

## When to use a business account

There are many use cases for business accounts. Here are four common ones:

<CardGroup cols={2}>
  <Card title="Company treasury" icon="building-columns">
    Shared wallets for operating funds. Teammates sign across them; add a server signer for routine automated moves like rebalancing. Admins manage who joins and who can sign as the team changes.
  </Card>

  <Card title="Platform for business customers" icon="sitemap">
    Provision wallets for other companies. Administer each customer's account — view activity, manage members — without signing by default. Add a server signer only when you need to move funds on their behalf.
  </Card>

  <Card title="Supervised consumer accounts" icon="users">
    A guardian administers the account; the end user signs day-to-day transactions. Keep administration and signing split so the guardian controls access while the user still approves what they spend.
  </Card>

  <Card title="User wallets with an agent" icon="robot">
    Give end users wallets and let an automated agent act for them. The agent is a server signer; the user stays a signer so they keep final approval.
  </Card>
</CardGroup>

## The model

A business account owns wallets. There are multiple levels of access available to configure, grouped into **Members** and **Signers**.

<Note>
  Being an admin does **not** let someone sign, and being a signer does **not** grant admin rights.
</Note>

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

**Signers** approve transactions and messages for a specific wallet. Removing a signer only revokes that person's ability to sign — the wallet and other signers stay intact.

## 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're a signer, you [sign transactions and messages](/docs/javascript/reference/business-accounts/signing) the same way as any embedded wallet.

## Next steps

<CardGroup cols={2}>
  <Card title="Create a business account" icon="plus" href="/docs/javascript/reference/business-accounts/create-a-business-account">
    Create an account and read back its details.
  </Card>

  <Card title="Add wallets" icon="wallet" href="/docs/javascript/reference/business-accounts/add-wallets">
    Create a fresh wallet or link an existing one.
  </Card>

  <Card title="Manage signers" icon="key" href="/docs/javascript/reference/business-accounts/manage-signers">
    Grant and revoke signing access.
  </Card>

  <Card title="Members & roles" icon="users" href="/docs/javascript/reference/business-accounts/members-and-roles">
    Administer membership and transfer ownership.
  </Card>
</CardGroup>