> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/overview/user-interfaces/quick-actions.md).

# Quick Actions

Kumu's Quick Actions menu is your one-stop-shop for useful functions, features, and how-to videos. If you can't quite remember where to find something in Kumu's [user interfaces](/overview/user-interfaces.md), you can use the Quick Actions menu to search the entire software.

To bring up the Quick Actions menu, click the magic wand on the [bottom toolbar](/overview/user-interfaces/map-editor.md#bottom-toolbar) or press `W` on your keyboard. You'll be greeted with a list of helpful options:

![quick actions modal](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-8a0058485804a48ced699727528561989a7ebfc8%2Fquick-actions.png?alt=media)

Search for the feature you're looking for, and the list of options will filter itself to match your keywords.

We're always adding new items to the list of options in the quick actions menu. If you think we missed something important, just email <support@kumu.io> and let us know!


---

# 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.kumu.io/overview/user-interfaces/quick-actions.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.
