> 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/products/integrations/reporting-and-notifications/proximity-and-contact-tracing-report.md). # Proximity and Contact Tracing Report The **Proximity and Contact Tracing Report** is a standalone contact-tracing application built on the Gallagher **REST API**. It analyses historical cardholder entry and exit events to work out who was in proximity to an "origin" cardholder, and outputs the result as a **`.csv`** report (viewable in Microsoft Excel or similar). It is **not a licensed feature**, but it uses the REST API licences (**`RESTCardholder`** and **`RESTEvents`**). Supported on **vEL7.90 or later**. ## Parameters The application provides a user interface to enter: * The **origin cardholder** * **From** and **To** dates * **Maximum in-zone time** * **Surface risk time** * **Maximum contact generation** * **Personal data fields** The report is built from access **events**, so it is only as good as the site's reader and access-zone configuration. No exit readers, tailgating, and split access zones for one physical space all reduce accuracy. See the FAQ below. ## How to obtain it * The feature is **not licensed**, but it uses the REST API licences (`RESTCardholder` and `RESTEvents`). * Customers **without** those licences can place a **$0 order for `C12846` LIC Proximity and Contact Tracing Report** and Gallagher will update their licence. * Customers who **already have** `RESTCardholder` and `RESTEvents` **still need** to place the $0 order for `C12846`. * Once the licence is updated, Gallagher provides a **link to download** the feature. * If the licence is updated but no download link arrives, contact Gallagher customer service (0800 84 2273) and request a download link. ## Configuration (worked example) A cardholder is identified as having had a contagious illness between **1 April and 5 April**. An operator wants to identify everyone who contacted them during that window: 1. Enter the **From/To dates** (1 to 5 April) in the utility. 2. Many of the site's Access Zones are **push-button exit** (no exit event), so set **Zone exit time to 8 hours**. The utility then assumes any cardholder who entered a zone had left within 8 hours (the "Maximum in-zone time" parameter). 3. Configure all Access Zones to be considered an **infection risk for 24 hours** after the source (ill) cardholder exited them. 4. Add **Personal Data Fields** to the export for each cardholder (for example department and email) so exposed cardholders can be contacted. 5. Select only the **relevant Access Zones** to report on, excluding very large, low-risk zones (for example outside areas) not at risk of contamination. 6. Run the report. It shows the source cardholder, then every cardholder ever in the same zone as the source, per the above configuration. Each "exposed" cardholder has a **contact generation** (level of contact): **direct** (contact with the source cardholder) or **indirect** (contact with someone who contacted the source cardholder). ## Frequently Asked Questions ### How do I get the Proximity and Contact Tracing Report utility? Please liaise with your Gallagher representative about how to get this functionality. ### What Command Centre version does the Proximity and Contact Tracing Report utility support? vEL7.90 or later. ### Is the Proximity and Contact Tracing Report a licensed feature? No, the feature is not licensed; however, it uses the REST API licenses (RESTCardholder and RESTEvents). Customers without these licenses can place a $0 order for C12846 LIC Proximity and Contact Tracing Report and Gallagher will update their license. Once the license is updated, Gallagher will provide a link via which the Proximity and Contact Tracing Report feature can be downloaded. ### My license already has the RESTCardholder and RESTEvents licenses, how do I access the Proximity and Contact Tracing Report feature? Customers that already have these licenses still need to place a $0 order for C12846 LIC Proximity and Contact Tracing Report and Gallagher will update their licenses. Once the license is updated, Gallagher will provide a link via which the Proximity and Contact Tracing Report feature can be downloaded. ### My license is updated, but I have not received a download link, who should I contact? If you have not received a download link after your license was updated, please contact Gallagher customer service (via 0800 84 2273) and request a download link. ### What happens if I do not have exit readers at some areas of my site? As the report is based on the events it will be able to report when an individual has entered the zone but it will not know when they have exited the zone. There is an option called "Maximum in-zone time" which can be configured so that the report will assume the individual has left a set number of hours after they have entered. ### What happens if people enter through a door without using their access credential? This application analyses events generated by Command Centre on cardholder movements through doors. If an individual follows another person through a door without using their access credential they will not be identified in the report. ### Will the report recognize contact if cardholders enter through different doors configured with different access zones into the same physical area? As the application analyses historical entry and exit events from an access zone, each access zone is treated as being a physical space. Doors that give access into a single physical space should be configured with the same access zone to ensure the reporting is as accurate as possible. *** 🔗 **Related** * [REST API - Features](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-features.md). The API this report is built on. --- # 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/products/integrations/reporting-and-notifications/proximity-and-contact-tracing-report.md?ask=&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.