> For the complete documentation index, see [llms.txt](https://play.equal.care/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/orientation-to-toc-tool-the-kumu-platform/toggling-between-views.md). # Toggling Between views To make it easier to explore our Theory of Change, we've created **multiple saved views** that highlight different parts of the map. These views allow you to focus on specific themes or areas without getting overwhelmed by the full picture. You can switch between these views using the **navigation bar at the top** of our map. 🎥 Watch how it works: {% embed url="" %} #### 🗺️ Interactive Map {% embed url="" %} 💡 **How to toggle views**: * Look for the **navigation bar** at the top of the embedded Kumu map. * Click on any named view (e.g. “Outcomes only”, “Inputs and Outputs”) to switch what’s visible. * Each view uses a mix of **focus** and **control functions** (covered above) to simplify what you’re seeing. *** The next pages will walk you through some of these views, showing how each one highlights a different part of our care model and the outcomes we aim to support. --- # 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://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/orientation-to-toc-tool-the-kumu-platform/toggling-between-views.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.