> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/quick-tips-for-configuring-voltage-report-layouts.md).

# Quick Tips for configuring Voltage Report Layouts

* The **Display graph** and **Display data table** checkboxes can be used to determine the report output format. By default only a graph of voltages will display.
* When displaying the data table, the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-65bdd58253f73d243ca718ca08533cf8ff2f68f0%2Freport_unsortedcolumnicon.png?alt=media) icon is the default that appears before an unsorted column name.
  * Click this icon to control sorting and grouping of columns.
  * Click and drag the column headers to reorder columns.
  * Click and drag column separators to resize columns.
* Headers, footers and a cover page are all optional for any report.
* When uploading report logos, only BMP, JPG, PNG and GIF image files, less than 5MB in size, are supported formats.
* When uploading report disclaimers, only RTF and TXT files, less than 5MB in size, are supported formats.
* The **Restore Default Configuration** button allows you to restore everything on this pop-up to a default layout for the report. Even after saving your changes and reopening this pop-up, clicking this button restores the default settings.


---

# 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://help.security.gallagher.com/knowledge-hub/command-centre-client/quick-tips-for-configuring-voltage-report-layouts.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.
