> 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/architecture/core-concepts/policies.md). # Policies Onchain permissions that constrain what a fund can do with its assets. 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/architecture/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 authorised 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 summarised 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kpk.io/funds/infrastructure/architecture/core-concepts/policies.md?ask=&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.