> 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/adjust-white-space-in-dashboard-panels.md).

# Adjust white space in dashboard panels

Sometimes you must adjust the white space in dashboard panels, (or the filter panel), so that content appears correctly. Use these steps to adjust white space.

1. In the lower pane, click **General Settings** and then click the **Properties** tab.
2. Click **Resize Panels**.

   The white space between the dashboard panels turns blue.
3. Adjust the panel size by clicking and holding the left mouse button down as you move the blue lines (white space) around. Release the mouse button when you are satisfied with the positioning of the panel.
4. Click **Close** in the lower-right corner of the dashboard to exit resize layout mode.
5. Examine the dashboard contents to make sure they are placed correctly.

   You can return to the resize layout mode if you need to make additional changes.


---

# 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/adjust-white-space-in-dashboard-panels.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.