> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-management/workbench/understanding-datasets/drills.md).
# Drills
Drills are a way of configuring what should be displayed to the end users when they interact with reports by clicking on charts.
It's a great way to:
* Allow your viewers to go beyond just a report aggregated data
* Add more interactivity to the report
## Why using drills?
When viewers will start consuming your reports, they will have additional questions.
> Why are my sales going up or down?
>
> What are the deals currently in closed won or lost? etc.
To give more flexibility and level of interaction to viewers, you can set up drills in the [Workbench](/data-management/workbench.md) that will then be automatically available to all your charts in the reporting section.
## How can I configure drills?
In the workbench, at the bottom left corner of your window, click on the "**Drills**" button
Configuring drills
From here you can pick any property you want to be available as a Drill and reorder them the way you want by dragging and dropping them.
{% hint style="info" %}
Please note that by default drills show the primary key
{% endhint %}
---
# 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.whaly.io/data-management/workbench/understanding-datasets/drills.md?ask=&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.
