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

# Report Filters

Report Filters are configured when a report is created, and provide the ability to filter event and alarm details, and cardholder details. There are two types of Reports Filters, (i.e. **Editable Filters** and **Non-editable Filters** ).

When you select a report, the screen is populated with a Filters panel on the left (to allow Editable Filters to be changed at runtime, and Non-editable Filters to be viewed), and a Preview panel on the right. The Editable and Non-editable areas are expanded by default but are collapsible up and down. The separation bar between the two sections can also be dragged up and down. Likewise, the entire Filters panel can be collapsed to the left (to expand the Preview panel) by clicking the **Filters** button.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-17e709b09f757829bfaac86391edef2d4d277541%2Freportfilters.png?alt=media)

**Editable Filters** are the report filter values that can be overridden (changed) at runtime. See below for the procedure.

<details>

<summary>Editing a Filter</summary>

**Note:** The **Edit this Filter** ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7c2828918c7cb681beaf46588ec4d5b23de9a63b%2Feditfilterbutton.png?alt=media) button is not available for Evacuation Reports. Instead, Evacuation Report filters, (i.e. an "Ignore old card events" filter, a "Select Access Zones" filter and the option whether or not to display Access Zones with no cardholders in them), exist permanently inside the collapsible ‘Filters’ section where they can be edited, but not added or deleted.

1. Click the **Edit this Filter** ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7c2828918c7cb681beaf46588ec4d5b23de9a63b%2Feditfilterbutton.png?alt=media) button.

   (Alternatively, you can double-click on the condition.)

   The Edit Condition pop-up displays and is populated with data relevant to the condition type selected.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9b59840a9958d1d875060eae775ef57186cc71b6%2Freport_editconditionpopup.png?alt=media)
2. Edit the condition as required, and click the **OK** button.

   The condition is altered accordingly in the 'Filters' section.

   **Note:** Each time a condition is edited, a **Refresh** button appears over the Report Preview, which can be clicked to update the preview.

</details>

**Non-editable filters** cannot be changed at runtime, but can be viewed by clicking the **View this Filter** ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7c2828918c7cb681beaf46588ec4d5b23de9a63b%2Feditfilterbutton.png?alt=media) button.

The Edit Condition pop-up displays in 'read-only' mode.


---

# 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/report-filters.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.
