> 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/pentaho-interactive-reports-cp/customize-an-interactive-report/design-report-headers-and-footers.md).

# Design report headers and footers

Double-click the upper or lower corners of the report to design your report headers and footers.

![Design Report Headers and Footers](/files/iYPDQ0gjPyJcMy8tUfED)

Use the dialog box to adjust any of the following options:

* Delete any existing words, or enter a new header and press Enter.
* Click **Date** and press Enter to insert a date and time stamp in the page header. You can customize the date and page count by adding your own text, such as `Today: $(report.date)`, instead of using the default $(report.date).
* Click **#/Pages** and press Enter to insert the number of pages in the 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pba/pentaho-interactive-reports-cp/customize-an-interactive-report/design-report-headers-and-footers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.