This is a map of the parameters that shape a module's behavior: what each one does and where it is explained in depth. The conceptual pages cover the mechanics; this page is the index to them from a configuration standpoint.
Almost every parameter is set by the Safe. A small set belongs to the Provider, and bridge route/OFT registration lives at the shared-infrastructure layer. For who can set what and why, see Permissions & Governance.
Roles
Parameter
What it controls
addOperator / removeOperator
Who may execute strategy actions (manage, swap, harvest, bridge).
addGuardian / removeGuardian
Who may pause the module.
Capability surface
Parameter
What it controls
See
setOperatingMode
The OPEN / FENCED / WALLED dial that decides which economic guards are live.
These bound the economic outcome of operations in guarded modes. All loss limits are expressed in basis points and capped at 100% (10000 bps) at configuration time. A cooldown of zero disables that cooldown.
Returns any ERC-20, ERC-721, ERC-6909, or native balance held by the module back to the Safe.
Provider-held parameters
These are set by the Provider, not the Safe. The Provider holds no power over strategy configuration or funds. The initial Provider and swap fee rate are fixed at deployment: supplied by the deployer on the permissioned path, or set to the factory defaults on the permissionless path. See Module deployment.
Parameter
What it controls
setSwapFeeRate
The swap fee rate, capped at 1e18 (100%) so the fee never exceeds the swap output.
suspend / unsuspend
A halt that blocks all Operator actions, independent of the Guardian pause.