> 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/quick-tips-for-configuring-the-entry-and-exit-readers-filter.md).

# Quick Tips for configuring the 'Entry and Exit Readers' filter

* When creating a Time Report, by default the **Entry and Exit Readers** filter is already added. You can edit this instance of this filter condition, but will not be able to add another instance of it.
* Readers and External System Items (ESIs) can be selected in this filter.
* **Grace Time:**

  Cardholders sometimes present their card a second time at a reader if they are unsure whether the reader read the card the first time. Grace Time defines the number of seconds where multiple card reads of the same card are considered to be one read. The first valid read is recorded as the entry or exit, and all subsequent reads within the grace time are ignored.

  (Default = 0 seconds for separate readers / 30 seconds for combined readers. Range = 0 - 600 seconds)
* **Include Time on Site when it is calculated based on assumptions:**

  When the Entry Time or Exit Time is an assumed time based on Report Rules then by default the report will include the 'assumed' value(s) in the ‘Time on Site’ column. However, if this option is unchecked, the report will show a null ‘Time on Site’ value, therefore excluding the assumed value(s).
* **Display only First Entry and Last Exit:**

  When this option is selected the report will only consider the first entry event and last exit event and hence determine one row per cardholder, per defined day. Time-On-Site can be calculated optionally with or without the interference of intermediate Exit/Entry events.
* **Configuration options around inclusion/exclusion of assumed entry/exit pairs:**

  <table><thead><tr><th width="346">Configuration option</th><th>Explanation</th></tr></thead><tbody><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f8e51a65bb71719a329c934261a6417abc814961%2Fentry%26exitreadersfilter1.png?alt=media" alt=""></td><td>Display all entry and exit badges and show actual and assumed (exception) Time on Site values.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4b9f737ad2ce8996d268f906754db14accc998c9%2Fentry%26exitreadersfilter2.png?alt=media" alt=""></td><td><ul><li>Display only First Entry and Last Exit.</li><li>Display Time on Site as the sum of all actual and assumed (exception) exit/entry pairs.</li></ul></td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7c985ae2d7404d66504f966380177dcad7a8497b%2Fentry%26exitreadersfilter3.png?alt=media" alt=""></td><td><ul><li>Display only First Entry and Last Exit.</li><li>Display Time on Site as the delta between the First Entry and Last Exit.</li><li>Always display the Time on Site even when first entry or last exit are assumed (exception).</li></ul></td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-47a34db2108c87176ed6aa1f16557c30fd1bb9d6%2Fentry%26exitreadersfilter4.png?alt=media" alt=""></td><td>Display all entry and exit badges, but do not include any assumed (exception) Time on Site values.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a77ec0c85b63d68d0a0204fcb688c790e6df0961%2Fentry%26exitreadersfilter5.png?alt=media" alt=""></td><td><ul><li>Display only First Entry and Last Exit.</li><li>Display Time on Site as the sum of ALL actual exit/entry pairs. Discard the assumed (exception) pairs when calculating.</li></ul></td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4b3fbce67d8503a2bdfd45a41e46f52f8f2d162f%2Fentry%26exitreadersfilter6.png?alt=media" alt=""></td><td><ul><li>Display only First Entry and Last Exit.</li><li>Display Time on Site as the delta between the First Entry and Last Exit.</li><li>Only display the Time on Site when the first and last values are actual badges. Show blank if first entry or last exit are assumed (exception).</li></ul></td></tr></tbody></table>
* **Include visitor on-site and departed events:**

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

  This section is only available when a site is licensed for Visitor Management.

  It allows workstations to be selected to include events related to those workstation(s) to trigger Entry and Exit report entries as per:

  * The event created when a visitor is marked On-Site in either the Visitor Management client or the Visitor Management Kiosk will be used as an Entry event.
  * The event created when a visitor is marked Off-Site in either the Visitor Management client or the Visitor Management Kiosk will be used as an Exit event.
  * The event created when a visitor is marked Temporary Off-Site in either the Visitor Management client or the Visitor Management Kiosk will be used as an Exit event.
  * The event created when a visitor is automatically marked as departed because they are in or have entered a configured departure zone at the end of a visit.

|   | <p>Note regarding the report output:</p><ul><li>The ‘Entry Point’ and ‘Exit Point’ columns in the report output are populated with the name of the Workstation.<br><br><strong>Note:</strong> Automatically departed events are not related to a workstation and are marked as 'Automatic Departure' in these same columns.</li><li>The ‘Entry Door’ and ‘Exit Door’ columns (when added to a report) display the Workstation also, unless the event is an auto departure event in which case the door column displays the division name.</li></ul> |
| - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

* **Allow change when report is run:**

  Checking this checkbox allows the filter to be edited at runtime.


---

# 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/quick-tips-for-configuring-the-entry-and-exit-readers-filter.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.
