> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/8.-paginated-reporting.md).

# 8. Paginated reporting

Inforiver provides options such as pagination, header & footer, and report layouts which allow you to build highly formatted & interactive paginated reports. In this section, we'll cover the following:

**1. Pagination** - Utilize First-Previous-Next-Last navigation, with the ability to insert row, column & section breaks dynamically based on category values (e.g., each category starts on a new page). To learn more, refer to [pagination](/working-with-inforiver/8.-paginated-reporting/pagination.md).

**2.** **Header & footer** - With Inforiver, you can configure the report header and footer using customizable preset layouts and add charts, KPIs, images and text. To learn more, refer to [header & footer](/working-with-inforiver/8.-paginated-reporting/header-and-footer.md).

**3. Report layouts** - With Report+, you can build no-code paginated reports using preset designs, header/footer formatting capabilities, row/column/section breaks, summary/list/comparison views and more in a matter of minutes. To learn more, refer to [report layouts](/working-with-inforiver/8.-paginated-reporting/report-layouts-report+.md).

**4. Display and themes** - Frequently used customization options such as toolbar & canvas theme, row highlight, major & minor gridlines that are available in ‘Display Settings’ are covered in [display and themes](/working-with-inforiver/8.-paginated-reporting/display-and-themes.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.inforiver.com/working-with-inforiver/8.-paginated-reporting.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.