> 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/2.-displaying-information/basic-formatting/insert-blank-rows.md).
# Insert blank rows
Financial statements and reports often require options to add white spaces for formatting. Premium Table provides the insert 'Empty Row' option to achieve this in a single click.
Select a row above which you would like to insert an empty row. Navigate to the Insert ribbon > Insert Row > select Empty Row.
Insert Row option
A blank row gets inserted above the 'Camera and camcorders' row as shown.
Empty row inserted
The Empty row option can also be accessed using the row gripper. Hover over the 'Computers' row. Click on the row gripper icon and choose the **Add Empty Row** option from the Insert section.
Inserting empty rows from the row gripper
Empty rows can be deleted by clicking the row gripper of the empty row and selecting the **Remove Empty Row** option.
Removing blank rows
In the next section, we'll look at the [basic inline charts](/premium-table/working-with-premium-table/2.-displaying-information/add-basic-inline-charts.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/premium-table/working-with-premium-table/2.-displaying-information/basic-formatting/insert-blank-rows.md?ask=&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.
