> 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/using-basic-control-functions.md). # Using Basic Control Functions Kumu’s control functions help simplify your map by letting you **filter or highlight different types of elements and connections**. This is especially useful when you're exploring a complex map like our Theory of Change, where you may only want to focus on specific categories or relationships at a time. ## What are control functions for? * **Filter out** information that isn’t relevant to what you’re looking at * **Explore categories** (like outcomes, outputs, or indicators) one at a time * **Navigate complexity** more easily during presentations or evaluations Watch the short video below to see how it works: {% embed url="" %} ## 🧪 Try it out below The embedded map beneath this section shows **all the elements and connections** in our Theory of Change. 🔍 **Use the control buttons** at the bottom of the map to: * Show or hide different types of nodes (e.g. outcomes, activities, indicators) * Change the visibility of connections between elements * Highlight specific themes or areas of focus {% embed url="" %} These controls allow you to move from the big picture to fine detail - and back again - without getting lost. --- # 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/using-basic-control-functions.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.