> 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/creating-a-new-report/site-configuration-report.md).

# Site Configuration Report

### Introduction

The Site Configuration Report allows an operator to obtain a hard copy record of the configuration for selected items. The report may be generated for any selected items within the operator's division. Items **not** reported on are: Crypt Seed, Facility Code, Cardholders, Access Groups, Personal Data Fields, Operator Groups and Operator Privileges.

Operators must have the "View Site" and "Edit Report Descriptions" privileges to create, save, edit and delete Site Configuration Reports. System division restricts the level of item information that an operator may view through the report.

**Note:** The Site Configuration Report can be used for Guard Tours, (i.e. it can list the checkpoints for a security guard to follow on a specific Guard Tour route, and indicate times allowed (and tolerances) between checkpoints).

The report can be run so that:

* text held in the **Notes** tab of a Guard Tour can be optionally displayed on the report (by checking the **Notes** checkbox on the **Report Style** page). This allows special instructions to be printed for the benefit of the guard.
* all other site configuration data is eliminated (on the **Select Items** page).

***

### Report Wizard

The Site Configuration Report wizard contains a number of pages which prompt you to enter certain information to create a report.

**Follow the instructions displayed**.

<details>

<summary>Report Style page</summary>

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

This is the first page of the Site Configuration Report and allows the operator to choose optional section(s) to include in the report, (i.e. either one or two, or all three options can be selected).

</details>

<details>

<summary>Report Options page</summary>

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

This page allows the operator to choose a primary and secondary sort key for the report. The default sort keys are 'Name' for the primary key, and 'Type' for the secondary key.

The operator can also choose whether to have each item printed on a separate page, or to have them printed continuously.

</details>

<details>

<summary>Select Items page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1bf14beb5523235944da0fe85d98f778e1e1de7d%2Fsc2.png?alt=media)

This page allows the operator to include specific items in the report, (i.e. all items or selected items). If the operator selects the radio button for all items, the **Next** button is enabled. If however the operator selects the radio button for selected items, the **Next** button will not be enabled until items have been placed in the selection box.

The operator can either use the Find Tool to search for items, and drag and drop them into the selection box as criteria for this report, or alternatively drag items from list windows.

</details>

<details>

<summary>Report Generation and Saving page</summary>

This wizard page is the same for all report types, and provides the same options. Refer to [Report Generation and Saving](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md) in the *Creating a new report* procedure for further detail.

</details>


---

# 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/creating-a-new-report/site-configuration-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.
