Skip to content

Organizations

An organization in Sigvault is a workspace shared between multiple users. Members of an organization can share their hardware signing devices with the org so that the keys they hold can be used to build multisig vaults that the whole org operates collaboratively.

Organizations are the right fit when:

  • A business wants a treasury vault co-signed by multiple employees
  • A family wants a joint vault held by family members in different households
  • A DAO or partnership wants governance over a shared treasury
  • An institution needs internal separation of duties for key custody

If you only need personal wallets, you don’t need an organization — Sigvault works fine with a single user.

Each organization has its own member list, device pool, and wallets. A single user can belong to multiple organizations at once and switch between them from the dashboard.

Sigvault is non-custodial by design. The organization does not hold anyone’s private keys. Instead, members contribute visibility to their devices: a member can choose to make one of their hardware devices selectable inside the org’s vault builder. Ownership of the device — and the seed phrase behind it — stays with the member who registered it.

When an org builds a multisig vault from contributed devices, every device owner is asked to explicitly consent to their key participating in that specific wallet. A vault is only provisioned once every selected device’s owner has accepted.

This means three layers of consent are involved before a key joins an org vault:

  1. Joining the org — the member accepts an invite
  2. Sharing the device — the member opts in to make the device visible to the org
  3. Per-vault participation — the member approves the specific vault their key is being added to

Any of those can be revoked.

  1. From the dashboard, open Organizations and click New organization. Give it a name.
  2. Open the org’s Settings tab and invite teammates by email.
  3. Once invitees accept (from their Inbox), they appear in the Members list.
  4. Each member opens their org and uses Settings → Device Shares to expose their hardware devices.
  5. An org admin opens Wallets → New wallet on the org, picks devices from the org’s pool, and sets the multisig threshold.
  6. Every device owner receives a key-participation request in their Inbox and accepts.
  7. The vault provisions and is ready to use.