A two-of-three wallet creates a signature threshold. Whether it creates two independent approvals depends on who controls the owners and which other execution paths the wallet permits.
The threshold is part of a wider configuration
Safe’s documentation describes owner accounts and a threshold for confirming transactions. It also documents modules that can introduce alternative access patterns, including execution without the usual confirmation process. Owner lists, thresholds and enabled modules therefore belong in the same configuration review. Safe documentation — Smart account architecture
Three addresses can still depend on one person
Imagine a treasury wallet with owners A, B and C and a threshold of two. If one employee controls both A and B, the wallet can satisfy its normal threshold without another employee’s approval. The on-chain structure contains three owners, but the human process contains fewer independent decision-makers.
Shared storage can create another dependency. Suppose two owners’ recovery information is accessible through the same administrator account. An incident affecting that account could compromise what initially appeared to be separate signing arrangements. Address count alone would not expose that concentration.
Availability must be considered alongside misuse. If two owners become unavailable at the same time, the remaining owner may lack the ability to execute an urgent transaction. Raising the threshold can increase approval requirements while making recovery harder. The appropriate arrangement depends on the actual organisation and its recovery design.
Now imagine an enabled module that can execute certain payments under its own conditions. Reviewing only transactions approved by owners would omit that path. The module might serve a legitimate purpose, but its permitted actions, limits and administrators need an explicit inventory.
For reporting, distinguish a technical statement from an operational conclusion. “Two owner confirmations are required on the standard path” is a configuration claim. “Two independent people must approve every outgoing transfer” is a broader claim requiring evidence about control and all applicable execution paths.
Review authority as a map
Document who controls each owner, how recovery works and which owners share dependencies. Inspect enabled modules and any other extensions that influence execution. Match the review to the deployed wallet rather than a generic product description.
After a staff departure or configuration change, repeat the authority review and preserve the change record. A multisig threshold can support governance, but the strongest evidence comes from independent control, understood permissions and a workable recovery process.