> 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/access-report.md).

# Access Report

### Introduction

The Access Report provides a list of Cardholders who can access a door/zone during a specified time period.

Operators must have the "Edit Cardholders", "Edit Report Descriptions" and "View Site" operator privileges to create, save, edit and delete Access Reports.

***

### Report Wizard

The Access 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-3daa44e4b01f51194be3d83fb8cd6151197cacc9%2Faccess1.png?alt=media)

This is the first page of the Access Report wizard. It allows the operator to select either a **detailed** or **summary** version of the report.

**Detailed Access Reports** include a list of Cardholders along with their Personal Data and allocated cards. This style of the report is orientated around Cardholders, with the report sorted by Cardholder name or Personal Data Field. This report style also shows the date range over which a Cardholders access applies, which is determined from activation and expiry times of temporary access.

**Summary Access Reports** are orientated around Access Groups, and do not contain Cardholder information.

</details>

<details>

<summary>Report Criteria and Format page</summary>

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

This page allows the operator to choose criteria for the report and set basic formatting features such as inclusion of a Personal Data Field (PDF) and the report's sort order. The **Access Zone** and **Door** fields are mutually exclusive in that the operator may only set criteria in one field or the other. The **Day Category** and **Date** fields are also mutually exclusive, and a date in the past cannot be selected. The time range fields are restricted to a single day, (i.e. they may not be set to cross midnight).

</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/access-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.
