> For the complete documentation index, see [llms.txt](https://docs.maple.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maple.finance/technical-resources/admin-functions/strategy-delegate-actions.md).

# Strategy Delegate

A Strategy Delegate owns exactly one Strategy Manager and the Underlying Strategy behind it. Globals records the binding in `strategyDelegates`, the Strategy Manager stores the address as `strategyDelegate`, and the strategy reads it live through `strategyManager.strategyDelegate()`. The role is trusted in the same way a Pool Delegate is. See [Strategy Manager](https://docs.maple.finance/technical-resources/strategies/strategy-manager.md).

## Lifecycle

1. The Governor or Operational Admin approves the address with `setValidStrategyDelegate`.
2. The Strategy Delegate calls `MapleStrategyDeployer.deploy()`, which requires `isStrategyDelegate(msg.sender)` and pulls the bootstrap deposit from the caller.
3. The Governor or Operational Admin calls `activateStrategyManager`. Funding is rejected until then.
4. To hand over, the Operational Admin calls `setPendingStrategyDelegate` and the new delegate calls `acceptStrategyDelegate`. The outgoing delegate does not sign anything.

A Strategy Delegate cannot be revoked while it still owns a Strategy Manager.

## Strategy Manager

The Strategy Delegate is always an Operator, even while the Underlying Strategy reports impaired assets. See [The impairment block](https://docs.maple.finance/technical-resources/admin-functions/liquidity-bot-actions.md#the-impairment-block).

* `fundStrategyManager` (Operator)
* `requestRedeem`, `cancelRedemption` (Operator, or the Pool Delegate of the named Pool Manager)
* `processRedemption` (Operator or Operational Admin)
* `setPoolManagerCap`, `setStrategyLiquidityCap` (shared with the Operational Admin)
* `acceptStrategyDelegate` (pending Strategy Delegate only)
* `multicall` (anyone, each inner call runs its own checks against the original caller)

The Strategy Delegate cannot call `upgrade`, `setPendingStrategyDelegate` or `setActive`, and cannot set `strategyCapOf` on a Pool Manager. That cap belongs to the Pool Delegate.

## Underlying Strategies

Alone:

* `setStrategyDelegateFeeRate` (the sum with `strategyProtocolFeeRate` must not exceed `HUNDRED_PERCENT`)

Shared with the Operational Admin, on all three strategies:

* `impair`
* `removeImpairment`
* `recognizeLoss`
* `setMetadata`

[Aave V3 Strategy](https://docs.maple.finance/technical-resources/strategies/aave-v3-strategy.md), shared with the Operational Admin:

* `recoverPosition` (only after a loss is recognized)
* `claimRewards`
* `setReferralCode`

[Sky Strategy](https://docs.maple.finance/technical-resources/strategies/sky-strategy.md), shared with the Operational Admin:

* `recoverPosition` (only after a loss is recognized)
* `setFallbackTout`
* `setReferralCode`

On the Aave V3 and Sky strategies every function above except `claimRewards` and `recoverPosition` reverts once `recognizeLoss` has been called.

[Allocation Strategy](https://docs.maple.finance/technical-resources/strategies/allocation-strategy.md), shared with the Operational Admin:

* `recognizeLossAndRemoveImpairment`
* `setYieldCap`
* `skim`

Allocation Strategy, shared with the Security Admin:

* `setPermissions`
* `setDeploymentCaps`
* `cancelYield`

The Strategy Delegate cannot set `strategyProtocolFeeRate` or `useVirtualUnderlyingBalance`. Those belong to the Governor and Operational Admin.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maple.finance/technical-resources/admin-functions/strategy-delegate-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
