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

# Manage Signers

> Grant and revoke the ability to sign with a business-account wallet.

<Note>
  Business Accounts are in **early access**. See the [overview](/docs/javascript/reference/business-accounts/overview) for the model.
</Note>

A **signer** can approve transactions and messages with a specific wallet. Signing access is separate from [membership roles](/docs/javascript/reference/business-accounts/members-and-roles). Adding a signer grants them access; removing one only revokes theirs. The wallet and other signers stay intact.

<Info>
  Only an owner or admin can add signers, and the caller must already be an **active signer** on that wallet. This operation requires [step-up authentication](/docs/javascript/reference/business-accounts/step-up-auth).
</Info>

## Add a signer

`addBusinessAccountSigner` grants signing access to a user and returns a `shareSetId`. Identify them by a known `userId`, or by an `identifier` + `identifierType`. For example, when you provide an email, the user is created if they do not exist yet. If adding the signer requires quorum approval, it returns a pending action instead — narrow it with `isBusinessAccountActionRequired`.

<Tabs>
  <Tab title="JavaScript">
    ```javascript theme={"system"}
    import { addBusinessAccountSigner, isBusinessAccountActionRequired } from '@dynamic-labs-sdk/client/waas';

    // Load both values from your secure storage.
    const password = await loadCurrentSignerPassword();
    const targetSignerPassword = await loadTargetSignerPassword();

    const result = await addBusinessAccountSigner({
      businessAccountId: account.id,
      walletAccount,                 // a WalletAccount the caller can sign with
      signerType: 'endUser',
      targetIdentity: { identifier: 'teammate@acme.com', identifierType: 'email' },
      password,
      targetSignerPassword,
    });

    if (isBusinessAccountActionRequired(result)) {
      // Quorum not met yet — no share set to use until it's approved.
      throw new Error('Adding this signer requires approval.');
    }

    const { shareSetId } = result;
    ```
  </Tab>

  <Tab title="React">
    ```tsx theme={"system"}
    import { useAddBusinessAccountSigner } from '@dynamic-labs-sdk/react-hooks';

    const AddSigner = ({ walletAccount, businessAccountId, password, targetSignerPassword }) => {
      const { mutate, isPending } = useAddBusinessAccountSigner();
      return (
        <button
          disabled={isPending}
          onClick={() =>
            mutate({
              businessAccountId,
              walletAccount,
              signerType: 'endUser',
              targetIdentity: { userId: 'user-123' },
              password,
              targetSignerPassword,
            })
          }
        >
          Add signer
        </button>
      );
    };
    ```
  </Tab>
</Tabs>

<ParamField path="walletAccount" type="WalletAccount" required>
  The wallet to add a signer to, from the caller's `getWalletAccounts()`.
</ParamField>

<ParamField path="targetIdentity" type="{ userId } | { identifier, identifierType }" required>
  Who to add: a known `userId`, or an `identifier` (e.g. email) plus its `identifierType`.
</ParamField>

<ParamField path="signerType" type="'endUser' | 'server'">
  Whether the new signer is an end user or a server signer.
</ParamField>

<ParamField path="password" type="string">
  Your password, when your key share is password-encrypted and you have not already unlocked it this session. It unlocks your own key share, and is never applied to the new signer's share.
</ParamField>

<ParamField path="targetSignerPassword" type="string">
  A separate developer-managed value that encrypts the new signer's key share before backup. It is required when wallet passwords are required by your environment, and optional otherwise.
</ParamField>

<Note>
  To set an initial policy for the new signer after creation, use the `shareSetId` returned by `addBusinessAccountSigner` with `createPolicy`. `addBusinessAccountSigner` does not accept `initialSignerRules` at creation time.
</Note>

## Passwords when adding a signer

A password encrypts one person's key share, not the wallet. `password` and `targetSignerPassword` protect different shares.

1. `password` unlocks your own key share so the reshare can run. If the share is already unlocked for this session, you can omit it.
2. The reshare mints a new key share for the signer you add. Your own share set is untouched.
3. The SDK encrypts the new share locally with `targetSignerPassword`, then sends only the encrypted share to Dynamic for backup.
4. Your application makes `targetSignerPassword` available to the target signer after authentication. They use it to recover their share, then replace it with a user-controlled password by calling `setWaasWalletAccountPassword`.

<Warning>
  If wallet passwords are required by your environment, omitting `targetSignerPassword` rejects the request before the reshare starts, with the error `A target signer password is required for this environment.` Otherwise, the field is optional and the SDK uses the environment's default encryption instead of a caller-controlled password.
</Warning>

Your application is responsible for generating, protecting, and retrieving `targetSignerPassword`. Derive it per signer, for example from a per-signer salt and a server-side secret held in your backend, and return it only over an authenticated request. Do not reuse the current signer's password. Dynamic's backup service does not receive the raw value. See [Creating a wallet with a developer-provided salt](/docs/javascript/reference/waas/password-encryption#creating-a-wallet-with-a-developer-provided-salt) for a derivation pattern you can reuse.

## Remove a signer

`removeBusinessAccountSigner` revokes a signer's access to a wallet. The wallet and every other signer are untouched.

<Tabs>
  <Tab title="JavaScript">
    ```javascript theme={"system"}
    import { removeBusinessAccountSigner } from '@dynamic-labs-sdk/client/waas';

    await removeBusinessAccountSigner({
      businessAccountId: account.id,
      walletId,
      signerId,
    });
    ```
  </Tab>

  <Tab title="React">
    ```tsx theme={"system"}
    import { useRemoveBusinessAccountSigner } from '@dynamic-labs-sdk/react-hooks';

    const { mutate } = useRemoveBusinessAccountSigner();
    mutate({ businessAccountId, walletId, signerId });
    ```
  </Tab>
</Tabs>

<Warning>
  You cannot remove the **last active signer** on a wallet because no one could approve transactions afterward. Add another signer, or remove the wallet, first.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Members & roles" icon="users" href="/docs/javascript/reference/business-accounts/members-and-roles">
    Administer who can manage the account.
  </Card>

  <Card title="Sign transactions" icon="signature" href="/docs/javascript/reference/business-accounts/signing">
    Use a signer's share to sign.
  </Card>
</CardGroup>