> 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-report-designer/add-report-elements-in-report-designer-cp.md).

# Add report elements

Most report elements can easily be added by dragging and dropping them from the **Palette** or the **Data** pane to one of the layout bands. In some cases, there are a few extra details that you should know before you dive into report creation. Certain sections below may apply to your project.

**Note:** You should resist the temptation to overlap elements in Report Designer. While the output may seem appropriate in the Preview window and in some kinds of report output, the HTML and Excel output formats will have unusual problems.

For information on adding report elements, see the following topics:

* [Report layout types](/pba-report-designer/add-report-elements-in-report-designer-cp/report-layout-types.md)
* [Add standard design elements](/pba-report-designer/add-report-elements-in-report-designer-cp/add-standard-design-elements.md)
* [Align elements](/pba-report-designer/add-report-elements-in-report-designer-cp/align-elements.md)
* [Add bands](/pba-report-designer/add-report-elements-in-report-designer-cp/add-bands.md)
* [Create sub-reports](/pba-report-designer/add-report-elements-in-report-designer-cp/create-sub-reports.md)
* [Placing inline and banded sub-reports](/pba-report-designer/add-report-elements-in-report-designer-cp/placing-inline-and-banded-sub-reports.md)
* [Refer to report elements by name or column position](/pba-report-designer/add-report-elements-in-report-designer-cp/refer-to-report-elements-by-name-or-column-position.md)
* [Create a table of contents](/pba-report-designer/add-report-elements-in-report-designer-cp/create-a-table-of-contents.md)
* [Create an index](/pba-report-designer/add-report-elements-in-report-designer-cp/create-an-index.md)


---

# 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-report-designer/add-report-elements-in-report-designer-cp.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.