Enterprise MultiSig for treasury governance
Enterprise MultiSig is role-based treasury governance for companies and DAOs. Unlike Team MultiSig where everyone is equal, it assigns distinct roles and weights — Owner, Signer and Security Admin — and supports whitelists and limits, managed from a web console.
Who is this for?
Enterprise MultiSig fits organizations that need separation of duties over a treasury: a company managing operating funds and reserves, a DAO with a mandate to control who can change the signer set, or any group where "who can approve a payment" and "who can change the rules" must be different people.
Roles and weights
| Role | Can do |
|---|---|
| Owner | Add/remove members, modify the signing mode and governance |
| Signer | Sign (approve) transactions |
| Security Admin | Set whitelist, spending limits and similar policy |
A participant can hold more than one role. Weight lets signers count for more or less under the signing mode — for example a 3-4 sign mode means four participants where at least three weight-votes are needed to spend. A separate Owner Sign Mode (e.g. 2-2) sets how many Owner signatures are required for governance changes like adding a member.
How do I set up an enterprise MultiSig?
Choose Enterprise in Permission Scenario
When creating the MultiSig, pick Enterprise MultiSig and select the network (the EVM family and TRON support post-creation changes to roles and mode).
Set Sign Mode and Owner Sign Mode
Sign Mode is the weight needed to spend; Owner Sign Mode is the signatures needed for Owner actions such as changing members.
Assign each participant's weight and roles
Give each participant a weight and one or more of Owner, Signer and Security Admin.
Join, deploy and operate
Participants join, you deploy the contract, and then join/deploy/send follow the standard flow for that network. Operate at scale from the web console.
Changing Owners/Signers and the signing mode after creation is an Enterprise MultiSig capability, currently on the EVM family and TRON. (Team MultiSig is fixed at creation.)
Managing at scale with the web console
Operators holding roles across many wallets use the MultiSig web console to review and batch-sign pending transactions in the browser, rather than signing each one in the app. Open it from the Web Console button on the Ownbit homepage and scan to log in — see the web console concept page.
Limits and trade-offs
- Role changes and weight changes are governance actions gated by the Owner Sign Mode — design that threshold carefully.
- Whitelists, limits and post-creation edits depend on chain support (EVM family and TRON for edits).
- More flexibility means more to configure — for simple shared funds, Team MultiSig is easier.
- The web console is a larger surface for reviewing data and batch-initiating/signing; there is no wallet-count limit, but it can only be logged into one MultiSig wallet at a time.
Frequently asked questions
What roles does Enterprise MultiSig support?
Owner (add/remove members and change the signing mode), Signer (approve transactions), and Security Admin (set whitelist and limits). A participant can hold more than one role.
What is Owner Sign Mode?
A separate threshold for governance actions. For example 2-2 means two Owner signatures are required to add or remove a member or change the signing mode.
What are weights?
Weights let signers count for more or less toward the spending threshold, so approval power can reflect seniority or responsibility rather than one-vote-per-person.
Which chains support enterprise features?
The EVM family (ETH, BSC, and similar) and TRON support modifying Owner/Signer and the signing mode after creation. Other chains fix configuration at creation.
Last updated:
Download Ownbit
Install the app, then set up a cold wallet or MultiSig for the workflow you need.