> 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/customize-toolbar-prompts.md).

# Customize toolbar prompts

Perform the following steps to customize your toolbar prompts:

1. In the **Data** box, click **Add**.

   The List Value dialog box appears.
2. In the **Label** field, enter the option name as you want it to appear to dashboard users.
3. In the **Value** field, enter the parameter source name.

   If using the Steel Wheels sample, enter `Classic Cars`.
4. Add labels and values for each parameter you want to filter. Click **Close** to exit the List Value dialog box.

   If you are filtering an Analyzer report and using a static list, you can add the option **All**. This option drops the filter from the report and shows all values.
5. In the Control Properties box, under **Initially Selected**, choose which item you want to appear first in the prompt list.

   Choose **Use First Value** to set the default to the first value in the list, or you can choose **Specify** if you want a specific value to appear first.
6. Click **OK**.
7. In the **Objects** pane, choose the title of the report you want to filter. Click the **Parameters** tab and choose the correct **Source** for the parameter from the list.

   The source should be the name of your prompt.
8. Click **Save**.


---

# 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/customize-toolbar-prompts.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.