> 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/using-command-centre/reports.md).

# Reports

### Introduction

The **Reports** tab provides a separate area from the Viewer and Administration functionality, for creating, editing and running the following types of reports:

<details>

<summary>Access Report</summary>

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

**Operator Privileges**

Operators can only create, edit or delete Access Reports in divisions where they have the "Configure Access Report" privilege.

</details>

<details>

<summary>Activity Report</summary>

The Activity Report is a tool for reporting exactly what has been occurring in the system. It is a query tool and is not expected to be used to print regular reports for filing purposes.

**Note:** In a multi-server environment, for any given server where event aggregation is enabled, an operator can run an Activity Report which incorporates events from remote site items. The Activity Report can be filtered by remote site items.

**Operator Privileges**

Operators can only create, edit or delete Activity Reports in divisions where they have the "Configure Cardholder and Activity Report" privilege.

</details>

<details>

<summary>Cardholder Report</summary>

The Cardholder Report allows the operator to print a listing of Cardholder information. The operator specifies a set of cardholders as criteria.

**Operator Privileges**

Operators can only create, edit or delete Cardholder Reports in divisions where they have the "Configure Cardholder and Activity Report" privilege.

</details>

<details>

<summary>Evacuation Report</summary>

**Introduction**

The Evacuation Report provides a list of cardholders present on a site. This can be used in an evacuation situation, such as a fire, and allows better management of evacuation situations and improved cardholder safety.

**Note:** In a multi-server system that uses Visitor Management (a licensable feature), visit data does not get replicated between servers. Therefore, the Evacuation Report cannot report on remote visitors.

**Prerequisites**

The Evacuation Report relies on cardholder location information, and is therefore only effective at sites where all cardholders swipe their cards every time they enter or exit an Access Zone.

**Operator Privileges**

To create a new Evacuation Report, or to delete or edit the properties of an existing Evacuation Report an operator must have the "Configure Evacuation Report" operator privilege in the Evacuation Report's Division.

</details>

<details>

<summary>Summary Activity Report</summary>

**Introduction**

The Summary Activity Report focuses on event statistics. By default it shows a graphical representation of events over a report time period. There is also an option to display statistics in table format so that the data can be exported to CSV. The report also allows grouping of time so that a trend can be shown, (e.g. Numbers of events per week over the past three months).

**Operator Privileges**

Operators can only create, edit or delete Summary Activity reports in divisions where they have the "'Configure Cardholder and Activity Report" privilege.

</details>

<details>

<summary>Time Report (either Detailed or Overview)</summary>

**Introduction**

The Time Report provides the ability to track hours worked by individual Cardholders. Door entry and exit events are used in the system to calculate hours worked by individual Cardholders. In general, a Door entry event is equated to a Cardholder clocking in or starting work, while a Door exit event equates to a Cardholder clocking out or ending work.

**Note:** In a multi-server environment, for any given server where event aggregation is enabled, an operator can run a Time and Attendance Report which incorporates events from remote readers. The Time and Attendance Report can be filtered by remote readers.

**Operator Privileges**

Operators can only create, edit or delete Time Reports in divisions where they have the "Configure Time Report" privilege.

**Detailed Time Report**

The detailed Time Report will show entry and exit times for cardholders that badge at selected readers. The time report will contain configurable Earliest Daily Entry Time (EDET) and Latest Daily Exit Time (EDET) boundaries. These boundaries will be used to define entry and exit times when a cardholder tailgates entry or exit, or badges before EDET or after LDET. The time report will produce one row for each continuous period of times between entry and exit pairs (Time on Site column). These may be actual or assumed exit and entry pairs.

**Overview Time Report**

The Overview Time Report will show a summary of total time based on cardholder attributes: Name, Card Type, Cardholder Division and PDF values.

The Overview report will contain similar filters as the Detailed report. The report can be used alongside all reader and time filter configuration options including EDET/LDET, Max Time on Site, Separate/Combined readers, First Entry/Last Exit, Grace Time, Display assumed time. The filters column in the table below shows the filters that differ from the detailed report.

**Note:** This report also includes the filter 'Total Days' that enables an operator to report the total days a Cardholder has been on site within a specified reporting period.

</details>

<details>

<summary>Voltage Report</summary>

**Introduction**

The Voltage Report is only available for customers licensed for Fence Controllers. It allows an operator to produce a report of logged volts for a Fence Zone. These results are displayed on screen as a line graph, which can be printed out, or saved to file as a CSV format.

**Operator Privileges**

Operators can only create, edit or delete Voltage reports in divisions where they have the "Configure Voltage Report" privilege.

</details>

<details>

<summary>Z20 Tuning Report</summary>

The Z20 Tuning Report is only available if your site is licensed for Disturbance Sensors. A ‘Diagnostic Mode’ override can be performed on Disturbance Sensors (via the **Status and Overrides** tab of the Disturbance Sensor properties in the Configuration Client). This override will last for up to 48 hours or until it is cancelled. Running a Z20 Tuning Report will provide tuning data recorded over the 48 hours.

**Operator Privileges**

Operators can only create, edit or delete Z20 Tuning Reports in divisions where they have the "'Configure Z20 Reporting" privilege. They also require the "View Site" privilege in each division for that division items to appear in the filters and to display data when the report is run.

</details>

Click on the following function that you want to perform to do this:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-magnifying-glass">:magnifying-glass:</i> Finding a Report</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/finding-a-report.md">Finding a Report</a></td></tr><tr><td><i class="fa-filter">:filter:</i> Report Filters</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/report-filters.md">Report Filters</a></td></tr><tr><td><i class="fa-print">:print:</i> Printing a Report</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/printing-a-report.md">Printing a Report</a></td></tr><tr><td><i class="fa-star">:star:</i> Report Favourites</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/report-favourites.md">Report Favourites</a></td></tr><tr><td><i class="fa-file-export">:file-export:</i> Exporting Cardholder Images</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/exporting-cardholder-images.md">Exporting Cardholder Images</a></td></tr></tbody></table>


---

# 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/using-command-centre/reports.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.
