> ## Documentation Index > Fetch the complete documentation index at: https://docs.trezu.org/llms.txt > Use this file to discover all available pages before exploring further. # Members and Roles > Discover how to manage your treasury's team members and their roles In Trezu, each treasury is a shared multisig account, where multiple members collectively control the treasury's assets and actions. No single member has unilateral control over the treasury, and to perform any action the team needs to reach consensus. Members You can manage your team members and their roles in the **`Members`** section in the left sidebar. *** ## Members A member in Trezu represents a wallet address that can participate in the treasury. Each member: * Connects using their own wallet (e.g. a browser wallet, mobile wallet, or hardware wallet) * Signs proposals and votes using that wallet * Acts independently from other members This is the core multisig concept: multiple wallets collectively control one treasury. No single member has unilateral control over the treasury's funds, and to perform any action the team needs to reach consensus. *** ## Roles & Permissions Roles define what actions a member’s wallet is allowed to perform within the treasury. There are three roles in a treasury: [**Requestor**](#requestor), [**Finance**](#finance), and [**Governance**](#governance). Each role has specific permissions that determine what actions members can perform within the treasury. Members can have multiple roles assigned, and will have the combined permissions granted by each of their assigned roles *** ### Requestor Allows members to create requests related to the treasury's funds (e.g. treasury transaction requests). #### Can * ✅ Create payment requests * ✅ Create staking, unstaking, and withdraw requests * ✅ Create asset exchange requests * ✅ Delete their own pending requests #### Cannot * ❌ Vote on any request *** ### Finance Responsible for voting on treasury transaction requests - those created by [Requestors](#requestor). #### Can * ✅ Vote to approve or reject requests created by Requestors #### Cannot * ❌ Create, edit or delete requests * ❌ Manage members or treasury settings *** ### Governance Responsible for configuring the treasury's settings and member configuration. Exercise caution when assigning the Governance role, as this role has extensive control over the treasury's settings. [Read More](#governance-is-the-highest-trust-role) #### Can * ✅ Create requests to add, edit, or delete members * ✅ Create requests to update the voting duration * ✅ Create requests to update the treasury's theme and logo * ✅ Set the treasury's voting threshold * ✅ Vote on any treasury configuration requests * ✅ Delete their own requests #### Cannot * ❌ Create financial requests (e.g., payments, staking) * ❌ Vote on financial requests created by Requestors *** ## Governance is the Highest-Trust Role The Governance role controls who has power in the system. Because Governance controls membership and voting rules, it should be treated as the highest-trust role in the treasury. Governance is intentionally powerful and not meant for day-to-day use. Best practice is to: * Assign Governance to highly secure wallets * Use high voting thresholds * Share Governance across multiple trusted members when possible Treasury safety comes from isolating and sharing authority, not from weakening permissions *** ## Permission Matrix The following table shows the actions each role can perform: | Action | Requestor | Finance | Governance | | --------------------------------------------------------- | --------- | ------- | ---------- | | Create Payment Requests | ✅ | ❌ | ❌ | | Create Stake Delegation Requests (Stake/Unstake/Withdraw) | ✅ | ❌ | ❌ | | Create Asset Exchange Requests | ✅ | ❌ | ❌ | | Vote on Treasury Transaction Requests | ❌ | ✅ | ❌ | | Create Add/Edit/Delete Member Requests | ❌ | ❌ | ✅ | | Create Voting Duration Update Requests | ❌ | ❌ | ✅ | | Create Theme/Logo Update Requests | ❌ | ❌ | ✅ | | Create Voting Thresholds Requests | ❌ | ❌ | ✅ | | Vote on Configuration Requests | ❌ | ❌ | ✅ | | Delete Own Pending Requests | ✅ | ❌ | ✅ | | Delete Others' Pending Requests | ❌ | ❌ | ❌ | *** ## Best Practices When assigning roles and permissions within your treasury, consider the following best practices: * **Use least privilege**: Grant only the roles needed for each member’s responsibilities * **Separate duties**: Maintain a clear separation between financial operations and treasury configuration, do not assign the Governance role to Requestors or Finance members * **Use voting thresholds intentionally**: Higher-risk actions (like configuration changes) should require more approvals * **Do regular reviews**: Periodically review assigned roles and permissions to ensure they align with your treasury's current needs * **Governance caution**: Exercise caution when assigning the Governance role, as this role has extensive control over the treasury's settings