> 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/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/use-content-linking-to-create-interactive-dashboards.md).

# Use content linking to create interactive dashboards

Depending on your needs, you can create a static dashboard, which contains content in each panel that is separate but related. For example, you may provide users with a bar chart that contains total sales figures by region. Additionally, you may provide a data table that displays sales details for each state in a specific region. You may also want to provide sales data associated with each salesperson in a specific region. The content in your dashboard is useful to dashboard consumers, but to make it more interactive, you may want to consider using content linking.

The content linking features in dashboards allow you to associate (link) content in one dashboard panel to content on another dashboard panel as long as query parameters have been defined. These features are particularly helpful for drilling down or for dynamic filtering; for example, when dashboard consumers explode a single slice in a pie chart to launch content in a data table associated with that pie slice. In this instance, dashboard consumers are moving from a summary view to a detailed view interactively.

You can use content linking if your dashboard panel contains a data table, chart, `.xaction`, `.prpt`, and Analyzer report.


---

# 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/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/use-content-linking-to-create-interactive-dashboards.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.