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

# Activity Report

### Introduction

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.

This report can be scheduled to run automatically at regular times (via Action Plans or scheduled Macros). For further information refer to [Automatically Generated Reports](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports.md) and [Configuring Report Scheduling](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-report-scheduling.md).

**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

<table><thead><tr><th width="306">Privilege(s)</th><th>is required to...</th></tr></thead><tbody><tr><td>"Edit Report Description" and either "View Events and Alarms" or "Edit Alarms"</td><td>create, view, edit, print, save and delete Activity Reports.</td></tr><tr><td>"View Events and Alarms" or "Edit Alarms"</td><td>create, view, edit, and print Activity Reports.</td></tr></tbody></table>

***

### Report Wizard

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

**Follow the instructions displayed**.

<details>

<summary>Reporting Dates and Times page</summary>

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

This is the first page of the Activity Report wizard. This page allows an operator to enter a start and end time for the report. Pre-defined periods are provided for simplicity, or custom start and end times can be entered.

The default option is set as **Today**, with the start and end Date/Time set to midnight to the current time.

The default value for **Last \[n] hours** is set as "8" hours (valid range is 1 - 999), with the idea that at a shift change an operator may want to run a report based on however many hours the last shift was. A standard shift would normally be 8 hours, hence the 8 hour default setting.

You can optionally **Schedule this report to run at specified times**.

</details>

<details>

<summary>Event Priorities page</summary>

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

This page provides a tree representation of all the event priorities, and allows the different priorities to be selected for inclusion in the report. Priority selection is indicated by a "tick" box and is made be clicking in the checkbox next to the name.

**Note:** The priority names are user-defined (via the **Event Priorities** tab of the Server Properties).

Check the **Only include escalated alarm** checkbox if you wish to run a report that will just have escalated alarms in it. An Activity Report with only escalated alarms will include the full alarm details for each escalated alarm.

</details>

<details>

<summary>Event Groups and Types page</summary>

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

This page provides a tree view representation of the Event Categories and types. Event type selection is indicated by a "tick" box and is made by clicking in the checkbox next to the event name. Clicking the icon expands or contracts that branch of the tree.

Selecting an event category also selects all it's sub-events. De-selecting an event category also de-selects all it's sub-events.

**Note:**

An online help file listing all the event/alarm messages can be accessed via the **Help** menu bar in Command Centre, and provides explanations of what each message means.

</details>

<details>

<summary>Select Cardholders and Operators page</summary>

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

This page provides a list of Cardholders that an operator may include in the report. Cardholders shown here are restricted to those under the Division of the operator.

The Find Tool may be used to locate Cardholders, which can then be dragged and dropped onto this page. Alternatively, you can open the **Access Group** List Window and drag and drop those Access Groups you require onto this page.

**Note:**

Only cardholders that are currently active within an Access Group will be reported on. Therefore, if you want the report to include 'expired' Access Group members, you need to select cardholders rather than Access Groups.

The "Automatic removal of expired members" from Access Groups will alter the information in the report depending on when the report is run.

Should you wish to delete a Cardholder or Access Group from your list on the right, **right click** on the item and click **Remove from List**.

</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-79fda8157488b42687e4e17f898293d7a0860b5d%2Factivity4.png?alt=media)

This page allows the operator to select the items they wish to report on, (i.e. all items or selected items by dragging and dropping them).

</details>

<details>

<summary>Regional Settings page</summary>

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

This page allows a time zone and/or language to be selected for the report. Selection of a time zone is optional, as it is only required for Command Centre sites that span time zones. Selection of a language is also optional as it is only required for sites that have multiple languages.

If no time zone is selected, the report uses the time zone of the Command Centre server, only if the report was initiated from a macro which was triggered by an Action Plan, or a macro that was run from its schedule. In all other cases, the report uses the time zone on the workstation of the operator who has run the report, or the time zone on the workstation of the operator who ran the macro that triggered the report.

If a time zone is selected, when the report is run, all dates and times within the report will display in the selected time zone. Any dates and times configured within the report are assumed to be within the selected time zone (rather than the time zone on the configuring operator's workstation).

</details>

<details>

<summary>Report Scheduling page</summary>

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

This page only displays if the "Schedule this report to run at specified times" checkbox is checked on the **Reporting Dates and Times** page. It allows run times and repetition properties to be defined for the report.

Multiple explicit times for the report to be run can be configured, as follows:

1. Click the **Run at** radio button.
2. Enter a date and time, and click the **Add** button.

   The date and time appears in the **Next Scheduled Run Times** grid.
3. Repeat Steps 1-2 for each explicit time you require.

   **Note:** If you click the **Repeats** radio button, then the explicit additions are removed from the **Next Scheduled Run Times** grid.

Repeat times for the report to be run can be configured, as follows:

1. Click the **Repeats** radio button.
2. Select the 'initial' **From** date and time.
3. Select an **Until** date and time if required.

   **Note:** If no **Until** date is entered, the report will repeat indefinitely.
4. Select the regularity for the report to be run, (i.e. **Every** one or many **Hours**, **Days**, **Weeks** or **Months** ).

   **Note:** When **Weeks** is selected from the drop-down list, the days of the week display with an ability to select one or multiple days, (e.g. Monday and Thursday).

   The next five dates and times appear in the **Next Scheduled Run Times** grid.

The **Division** selection grid allows the report to be scheduled for specific divisions.

**Note:** Only Divisions to which you have the appropriate editing privilege will appear in the drop-down list.

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