Connecting a Safe
Connecting a Safe lets its owners operate the Aragon app as the Safe, with the Safe itself as the connected actor.
How it works
The Safe can connect through either of two routes:
- Inside Safe: select the Safe on the required network, then add Aragon through Apps → Add Custom App. Safe opens Aragon inside an iframe. When Aragon detects that Safe environment, it connects automatically through the Safe Apps connector, which exchanges wallet requests with the surrounding Safe interface. This route needs no WalletConnect pairing code. See Safe's custom-app instructions and Safe Apps integration.
- Through WalletConnect: open Aragon directly and choose Connect wallet → WalletConnect. Copy its pairing code into Safe's WalletConnect control and approve the connection for the selected Safe. The network must be supported by both sides. See Safe's WalletConnect instructions and Aragon's wallet-connection dialog.
If the embedded app does not connect automatically, use the WalletConnect route from Aragon opened directly. Before submitting an operation, check that the connected address is the intended Safe and that its network matches the operation. Signing requests then follow the Safe's approval flow; connecting does not grant the Safe a role or permission it does not already hold.
When it's used
Connecting as the Safe is what lets the Safe itself — the account, not an Aragon multisig — act in Aragon wherever it has a role to play:
- Approving its stage of a staged proposal when the Safe is a governing body — see Safe as a body.
- Creating a proposal on a process the Safe holds a direct proposal-creation permission for — see direct creation grant to a Safe.
- Acting as the connected actor on an account the Safe holds Execute permission on — see executing on a linked account.
Last updated on