Check from the ledger whether an account hangs from a single seed phrase or is shielded by an Access Controller, and where its owner badge actually is.
Reads from the ledger who controls the account: its key, or an owner badge. If it is a badge, it also says where that badge lives. Read-only: nothing is signed and nothing is sent.
What can be done today with the Radix Wallet, and why this console does not create multi-signature accounts.
The wallet only signs with its own keys
For two people to approve the same transaction, someone has to gather their signatures and submit it. That needs a separate service coordinating the signers; it is not something a web page can set up without holding anything in custody.
Setting it up by hand can lock you out
Radix Wallet shields use the same mechanism (an Access Controller holding the owner badge). If a website configures one on its own, the wallet may no longer know how to sign for that account, and there is no way back.
What does work: a shield with several factors
Create a shield in the wallet that requires two factors to sign, for example this phone and an Arculus card. If another person keeps the card, no transaction goes out without both. You have to be together to sign, but control is truly shared.
For group treasuries
A DAO or team that votes every payment needs its own component (a multi-signature blueprint) or a governance tool. Review its code or audit before putting funds in.