> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-dashboard-designer-cp/advanced-topics/use-prompts-on-dashboards/other-prompt-types/create-a-toolbar-prompt.md).

# Create a toolbar prompt

You can create a toolbar prompt which enables users to refine report results in a dashboard. First, create the prompt toolbar. Then customize the toolbar so the appropriate options appear.

1. Open a dashboard which contains at least one parameterized report.
2. Click the **Edit Content** icon to open the editing options in the dashboard.
3. In the bottom section, inside the **Objects** pane, choose **Prompts** to access the **Prompt** pane.
4. Click **Show Prompt Toolbar** to display the prompt toolbar to dashboard users.
5. Click **Add** to add a prompt.

   The Prompt dialog box appears.
6. In the **Name** field, enter the title for the prompt toolbar.
7. In the **Control** box, click the format for the prompt options.

   For example, you can choose the drop-down control if you want a list which appears when users click the first option.
8. Ensure that **Static List** is selected under **Type**.


---

# 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.pentaho.com/pba/10.2-analytics/pentaho-dashboard-designer-cp/advanced-topics/use-prompts-on-dashboards/other-prompt-types/create-a-toolbar-prompt.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.