> 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-the-focus-function-in-kumu.md).

# Using the focus function in Kumu

Kumu’s **Focus** tool lets you temporarily highlight just one part of the map, helping you cut through the complexity and explore relationships in a more manageable way. It’s especially helpful when explaining the map to others or zooming in on a specific theme or pathway.

## What does it do?

Focus hides everything except the element(s), connection(s), or loop(s) you’ve selected - and anything directly linked to them. It’s a simple but powerful way to see just one part of the system at a time.

## How to use it

You can activate Focus in two ways:

* **Click and hold** on any element, connection or loop
* **Click the element**, then click the **Focus icon** on the right-hand panel

Once in focus mode, you can:

* Use the ➕ and ➖ buttons to walk in or out by degree, revealing more or fewer connected elements
* Click the **Focus icon again** to reset the view and bring the full map back

👉 [See full guide in Kumu’s documentation](https://docs.kumu.io/guides/focus)

## Visual Example

<div data-full-width="true"><figure><img src="https://docs.kumu.io/~gitbook/image?url=https%3A%2F%2F1181816445-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FkXSW1nEf49ISqGxYuRfS%252Fuploads%252Fgit-blob-22dd313479c7ed7d737a7026026d3f270d5a7f8a%252Ffocus-expand-contract.gif%3Falt%3Dmedia&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=80def2d3&#x26;sv=1" alt=""><figcaption></figcaption></figure></div>

Click the focus icon again to bring the full map back into view.

Ref. <https://docs.kumu.io/guides/focus>

## Applying it to our Theory of Change

Here’s how this looks in practice using Equal Care’s map:

<figure><img src="https://1956200314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN8VA8CjNRwZEdN7ikK%2Fuploads%2F7uz7bid2587U1VsdffeD%2Fezgif.com-animated-gif-maker.gif?alt=media&amp;token=b20fd63d-dab2-44b5-b490-885346975c98" alt=""><figcaption></figcaption></figure>

This function helps you explore key outcomes, outputs or activities in more detail without losing the bigger picture.


---

# 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://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/orientation-to-toc-tool-the-kumu-platform/using-the-focus-function-in-kumu.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.
