> 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/configuring-command-centre/creating-reports/configuring-a-z20-tuning-report-layout.md).

# Configuring a Z20 Tuning Report Layout

1. Click the **Configure Layout** button that appears over the Report Preview in the Configuration Panel.

   The Report Layout Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-12c738a98d7642d84461b26a45446b64f6597d21%2Fz20tuningreportlayoutconfigurationpopup.png?alt=media)

   This pop-up is used to set the page layout options, (i.e. page size and orientation).

   **Note:** The following four columns are selected by default and are non-configurable:

   * Sensor Name
   * Date time
   * Dynamic value
   * Tilt value

### Changing the page layout

Change the default Page Layout options if necessary, (i.e. **Page Size** and **Page Orientation** ), as follows:

2. Change the **Page Size** if required.

   **Note:** The page size defaults to the last page size used by the operator (via operator preference) or to A4 if this is the first use of reports for an operator.
3. Select 'Landscape' from the **Page Orientation** drop-down list if you want the orientation of the report layout to be 'Landscape' rather than the default of 'Portrait'.

   **Note:** If page size and/or orientation changes are made, the **Column Configuration** section (in the lower part of this pop-up), changes to show the new aspect ratio of the page size selected, and column widths automatically adjust to fit the new orientation.

### Configuring Headers, Footers and Cover page

4. Click the **Configure Header/Footer/Cover Page** button.

   The Header, Footer and Cover Page pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-abec43b65667943bb7436fd8802c43fa13252e1f%2Freport_headerfootercover.png?alt=media)
5. Tick the relevant checkboxes for what you want to display on the report, (i.e. a Cover page, headers and footers).

   **Note:** The **Display Header** and **Display Footer** options are selected by default.
6. Do you want to upload a logo for the cover page and/or header on the report?

   If **yes**, go to Step 7.

   If **no**, go to Step 10.
7. Click the **Upload Logo** button.

   A **Select Image to Upload** dialog displays.
8. Path your way to the required image file.

   **Note:** Only BMP, JPG, PNG and GIF image files, less than 5MB in size, are supported formats for report logos.
9. Click the **Open** button.

   The dialog closes and the **Upload Logo** button changes to the name of the image file you selected.
10. Do you want to upload a disclaimer or other appropriate details for the report?

    If **yes**, go to Step 11.

    If **no**, go to Step 14.

    **Note:** If you upload a disclaimer file and do NOT select the **Display Cover Page** option, the disclaimer file contents will replace the cover page. However, if the **Display Cover Page** option is selected then the disclaimer file contents will be appended to the cover page contents.
11. Click the **Upload Disclaimer** button.

    A **Select File to Upload** dialog displays.
12. Path your way to the required image file.

    **Note:** Only RTF and TXT files, less than 5MB in size and no bigger than approximately 20 pages, are supported formats for report disclaimers.
13. Click the **Open** button.

    The dialog closes and the **Upload Disclaimer** button changes to the name of the file you selected.
14. Click the **OK** button.

    The Header, Footer and Cover Page pop-up closes, and returns you to the Report Layout Configuration pop-up.
15. Click the **OK** button.

    The Report Layout Configuration pop-up closes. The following message may display above the Report Preview in the Configuration Panel:

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-152b56e2d2cc9e289f4ea86c9d4ff08187386035%2Freportconfig_refresh.png?alt=media)

    If so, click the **Refresh** button. The Report Preview updates to reflect the configuration options selected.

    **Note:** If there are too many data points ( > 130,000) a pop-up will display.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ec0f69ca6a912a33c0a4658d4b4e1f804549589b%2Fz20tuningreport_toolargepreview.png?alt=media)

    The **Save to CSV** button allows you to retrieve the data in the report by exporting to CSV.

    Clicking the **Cancel** button returns you 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 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/configuring-command-centre/creating-reports/configuring-a-z20-tuning-report-layout.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.
