> For the complete documentation index, see [llms.txt](https://docs.kpk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpk.io/funds/infrastructure/core-concepts/policies.md). # Policies Policies define the set of onchain permissions that govern how a fund may operate. They are enforced through the [Zodiac Roles Modifier](https://github.com/gnosisguild/zodiac-modifier-roles), which acts as a programmable permission layer in front of each fund's Portfolio Safe. Because the Portfolio Safe's only owner is the `Empty` contract, **no key can move the fund's assets directly** — every transaction must pass through the **Exec Roles Modifier** (and, for automated flows, the nested **Sub Roles Modifier**). See [Roles and operators](/funds/infrastructure/core-concepts/roles-and-operators.md) for the full stack. Policies specify which actions can be executed on behalf of the fund — for example interacting with a specific DeFi protocol, managing a liquidity position, or initiating an approved bridging transaction — down to the target address, function selector, and parameter level. Any operation that falls outside the authorized policies is **blocked at the contract level**. This framework lets day-to-day portfolio management run smoothly while keeping the fund strictly confined to its risk profile and predefined execution rules. Each fund's current configuration is available in the dashboard's **Policy** view and summarized on its **Policies and addresses** page. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kpk.io/funds/infrastructure/core-concepts/policies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.