> 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/printing-an-existing-report.md).

# Printing an existing report

### Introduction

Once a report has been created and saved, it is displayed within the **Report Description** List Window. At any time you can select this report and print it out, providing you have the correct operator privileges. This will depend on the operator who originally created the report, and what [division](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#division) they are in.

### 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. Highlight the **required report**.
3. **Right click** and select **Properties**.
4. Click the **Next** button on each screen until you get to the "Report Generation and Saving" screen.
5. Click the radio button beside **Printer**.
6. Select the required printer from the drop-down list of available printers.
7. Click the **Setup Printer...** button if you need to set information about the printer, (e.g. paper size, or printing more than one page on a single sheet of paper). See [Customising Report Printouts](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/customising-report-printouts.md) if you require further detail.

   Once printer settings are made, click the **OK** button to return to the "Report Generation and Saving" screen.
8. Click the **Next** button.

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

### Result

The report is printed.

Depending on the settings when the report was created, the report may print to one of the following destinations:

* to the screen
* a hardcopy is printed
* to a file

### Hints

{% hint style="info" %}

* An alternative method to print is via the (right click) Properties option. Step through the wizard until the "Report Saving" screen displays. This method enables you to make any necessary changes to the report.
* If a specific selected printer is not available, the report is directed to the default printer.
* If the default printer is not available, the report is directed to the print preview (on screen).
* When the report is saved to file, the file can be opened using Microsoft Excel or Access. This enables various sorting and data Extraction tools to be used, such as Excels Data, Filter, Auto Filter or Access Queries.
  {% endhint %}


---

# 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/printing-an-existing-report.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.
