> 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/configuration-client/site-management/reports/customising-report-printouts.md).

# Customising Report Printouts

### Introduction

Printer settings can be altered, depending on the printer you are using, to customise how a report will print out, (e.g. paper orientation, double-sided printing, multiple pages per sheet, etc.). This can be achieved for both new reports and reports that have already been created and saved.

The following example provides instructions for how to alter your printer settings so that a report will print multiple pages on one sheet of paper (to reduce the amount of paper used).

#### EXAMPLE: Printing multiple pages per sheet

### Procedure

1. Click **Report** from the menu bar, then **Report Descriptions**.

   The **Report Description** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Either:
   * select an already saved report, or
   * **right click** and select **New**, and then the required report type.
3. Using the **Next** and **Back** buttons, step through the report wizard choosing appropriate report settings on each screen until you get to the "Report Generation and Saving" screen.
4. Click the radio button beside **Printer**.
5. Select the required printer from the drop-down list of available printers.
6. Click the **Setup Printer...** button.

   The **Print Setup** screen displays.
7. Click the radio button for the orientation you require, (i.e. Portrait or Landscape).
8. Click the **Properties** button.

   By default the **Paper/Output** tab of the Printer properties displays.
9. If you want the report to be printed double-sided, (i.e. on both sides of each sheet of paper), select "2-Sided Print" from the **2-Sided Print** drop-down.
10. Click the **Layout/Watermark** tab and select the required number of pages per sheet from the options under **Pages Per Sheet (N-Up)**.
11. Click the **OK** button.

    The **Print Setup** screen re-displays.
12. Click the **OK** button.

    The "Report Generation and Saving" screen re-displays.
13. Click the **Save Report** button if you wish to save this report.

    **Note:**

    Ignore this step if you are re-running an already saved report, as the **Save Report** button is disabled.
14. Click the **Next** button.

    The Report prints to the printer indicated.
15. Click the **Finish** button to return to the **Report Description** List Window.

### Result

The report is printed.

**Important:**

Any deviation from the above procedure can cause the report to return to the default settings, and not print as you expected. For example:

* If you do Steps 1-13, and then exit, when you do re-run the report, it will use the default settings, (i.e. single-sided and one page per sheet).
* If you do everything, but at Step 4 you click the **Print Preview** radio button instead of the **Printer** radio button, again, the report will run using 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/configuration-client/site-management/reports/customising-report-printouts.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.
