> 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-consumption/exploring-data/how-to-explore-data.md).

# How to explore data

## Explore from your workspace

From your workspace tab, you can access all exploration your builders have created for you. In order to access all explorations from your workspace, click on **Explore** at the top of the [Content Selector](https://docs.whaly.io/workspace/workspace.md). Please note that only [editor](https://docs.whaly.io/organisation/manage-access-control.md#editor) and [higher roles](https://docs.whaly.io/organisation/manage-access-control.md#builder) have access to explorations.

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2Fke2WfwmO0VQ8GAweeoCS%2FScreen%20Cast%202022-09-08%20at%2010.27.15%20AM.gif?alt=media&amp;token=090d22e6-d735-4643-ada1-d2029ec3bb66" alt=""><figcaption><p>Explore from workspace</p></figcaption></figure>

## Exploring from Report

From a question or a dashboard you can **hover the tile** to click on the **three dots** and click on the **Explore from here** menu. This will open the query in exploration mode allowing you to dig deeper into your analysis. Please note that when you are exploring data you are NOT modifying the query of the chart making it safe for your user to explore without breaking anything.

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2F8fYdfr1NVqVtv7GIUNDd%2FScreen%20Cast%202022-09-08%20at%2010.32.25%20AM.gif?alt=media&amp;token=4395ffd8-2fc0-429e-a833-5e2e60c14a64" alt=""><figcaption></figcaption></figure>

## Using explorations

The exploration page is divided into three main panels:

* The measures panel
* The visualisation panel
* The options panel

![](https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2FNMQgaVOhRM3ChHSapDzv%2Fimage.png?alt=media\&token=1da97257-1191-42aa-9e49-96fe47743ec5)

### Measures panel

The measure panel, on the left, contains your data tables, as well as their metrics and dimensions. In this panel, you can see the parent data table at the top level. On the exemple above, we can see that the exploration start from the Order table, and that we have added our order and our customer tables as related data.

We can also see multiple metrics (in blue) and dimensions (in green).

### Visualisation panel

The central panel, at the center, is divided into two groups:&#x20;

* First is the query builder, where you use metrics and dimensions in order to ask a question about your data.
* Then, under the "run query" button, you can see the actual visualisation which is the graphical representation of your query as defined in the query builder.

### Options panel

The options panel contains all styling options related to your current chart, for example you can show or hide labels, customise your series names and colors, ...


---

# 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-consumption/exploring-data/how-to-explore-data.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.
