> 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/premium-table/working-with-premium-table/7.-paginated-reporting/pagination.md).
# Pagination
Pagination refers to the organization of content into pages, usually with page numbers, in order to make it easier to read and navigate through the document. This also allows for easy printing and distribution of the report.
Let's discuss the single & multi-page options and pagination controls. In the Design ribbon, you'll find two options - ‘Single page’ and ‘Multi pages’.
Pagination options
### 1. Single page
'Single page' displays all the rows on a single page with a scroll (depending on the number of rows). Notice how all 880 rows in the report are displayed on the same page.
All rows displayed in a single page
### 2. Multiple pages
By using the 'Multi pages' option, you can automatically display the rows that fit on a single page and split the report into multiple pages. In the example below, you can see that the table is split into 34 pages.
Multi page report
### **3. Pagination controls**
When using the 'Multi pages' option, the following details are displayed in the status bar: Total rows, scrolling options to the first, last, previous & next page, and count of rows displayed on the page.
Pagination controls
You can also turn off pagination from the footer. Hover over the footer and click the  icon. In the footer context menu, disable the **Pagination** toggle. All the rows will be displayed on a single page.
Disabling pagination from the footer
In the next section, we'll look at adding a [header and footer](/premium-table/working-with-premium-table/7.-paginated-reporting/header-and-footer.md) to 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.inforiver.com/premium-table/working-with-premium-table/7.-paginated-reporting/pagination.md?ask=&goal=
```
`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.