> ## Documentation Index > Fetch the complete documentation index at: https://yieldxyz.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Roles & signing models > The role model that gates Meta Vault operations, and who typically signs for each deployment. A Meta Vault gates every privileged operation behind a role, so no single key controls composition, allocation, fees, and emergency pausing at once. End users never need a role: they interact only through the standard `deposit`, `mint`, `withdraw`, and `redeem` functions. ## Role reference | Role | Gates | | - | - | | Admin | Role administration: granting and revoking every other role | | Pauser | Halting deposits, mints, withdrawals, and redemptions | | Configurator | Setting fees and the fee recipient, and wiring in the compounding pipeline | | Strategist | Changing which strategies are whitelisted | | Rebalancer | Updating target weights, triggering a portfolio rebalance, and moving capital into or out of a specific strategy | | Harvester | Realizing management and performance fees, and triggering reward compounding | Role names describe what each one is for; splitting configuration, allocation, and emergency controls into separate roles means a single compromised key cannot do all three. The scopes above describe each role's purpose on the deployed Meta Vault contract. yield.xyz holds and operates these roles; confirm the exact function gating with yield.xyz before assigning any role to your own signer. ## Who signs The wallet or account that executes a Meta Vault's day-to-day operations (weight updates, rebalances, and manual allocation moves) varies by deployment: * **A dedicated signer.** Some deployments use a wallet scoped to only the operating roles it needs, most commonly the rebalancer role. It holds no admin authority, so it cannot grant or revoke roles or change the strategy set on its own. * **A client-controlled multisig.** Other deployments route the same operations through a multisig the client controls, so a proposed weight or strategy change requires the client's own signers to review and approve it before it executes. Which model applies to a given Meta Vault, and whether its weight updates are proposed automatically or set manually, is agreed with yield.xyz when the vault is configured. See the [dashboard guide](/guides/dashboards/meta-vaults) for how a deployment's configuration is requested. ## Next steps The strategist and rebalancer roles in action. A contract-level view of these roles and controls. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.