> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-widgets-guide.md).
# VerifEye Widgets Guide
**VerifEye** widgets allow you to visualize alarm data, agent activity, and site rankings directly on your Solink Dashboard. Follow the instructions below to create and configure each specific widget.
**Note**: See [Create a Report](/docs/understand-your-business/search-and-save-reports/create-a-report.md) for a general guide on creating reports. See the [Create Widgets](/docs/understand-your-business/create-widgets.md) guides for more information on widget creation.
## 1. All Alarm Verification
View the total number of alarm events processed through the VerifEye service.
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* **Widget Type:** Report
* **Graph Type:** Number
* **Report:** VerifEye - All Alarm Verifications
* **Category:** Other
* **DataType:** Bookmarks (Count)
* **Statistic:** Count
* **Name:** “VerifEye - All Alarm Verifications”
* **Tag:** “Alarms”
***
## 2. Verified Alarms
Track the total number of alarms that were confirmed as real alarm events.
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* **Widget Type:** Report
* **Graph Type:** Number
* **Report:** VerifEye - Verified Alarms
* **Category:** Other
* **DataType:** Bookmarks (Count)
* **Statistic:** Count
* **Name:** “VerifEye - Verified Alarms”
* **Tag:** “Alarms”
***
## 3. Unverified Alarm Events
View total number of alarm events that were not processed through VerifEye.
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* **Widget Type:** Report
* **Graph Type:** Number
* **Report:** VerifEye - Unverified Alarm Events
* **Category:** Other
* **DataType:** Bookmarks (Count)
* **Statistic:** Count
* **Name:** “VerifEye - Unverified Alarm Events”
* **Tag:** “Alarms”
***
## 4. False Alarm Categories (Reports)
Use these settings to create widgets for specific false alarm reasons as determined by VerifEye agents.
### False Alarm - Person in a public area
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* Widget Type: Report - "VerifEye - False Alarm - Person in public area"
* Graph Type: Number
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Name: “VerifEye - False Alarm - Person in public area”
* Tag: “Alarms”
### False Alarm - Employee
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* Widget Type: Report - "VerifEye - False Alarm - Employee"
* Graph Type: Number
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Name: “VerifEye - False Alarm - Employee”
* Tag: “Alarms”
### False Alarm - Contractor
Create a report with the following filters, then use this report to create a widget:
**Widget Configuration Settings:**
* Widget Type: Report - "VerifEye - False Alarm - Contractor"
* Graph Type: Number
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Name: “VerifEye - False Alarm - Contractor”
* Tag: “Alarms”
### False Alarm - Delivery
Create a report with the following filters, then use this report to create a widget:
* Widget Type: Report - "VerifEye - False Alarm - Delivery"
* Graph Type: Number
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Name: “VerifEye - False Alarm - Delivery”
* Tag: “Alarms”
### False Alarm - No person detected
Create a report with the following filters, then use this report to create a widget:
* Widget Type: Report
* Graph Type: Number - "VerifEye - False Alarm - No person detected"
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Name: “VerifEye - False Alarm - No person detected”
* Tag: “Alarms”
***
## 5. Ranking Widgets
Ranking widgets help you identify the highest-activity locations or verifiers.
### Alarm Verification: Store Ranking
View which locations have the highest volume of processed alarm events.
**Widget Configuration Settings:**
* Widget Type: Ranking
* Graph Type: Number
* Report: VerifEye - All Alarm Verifications
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Ranking Type: Location
* Max items displayed: Ex. 10
* Ranking order: Descending
* Name: “VerifEye - False Alarm - No person detected”
* Tag: “Alarms”
### Alarm Verification: Verifier Ranking
View which VerifEye agents have processed the most alarm events.
**Widget Configuration Settings:**
* Widget Type: Ranking
* Graph Type: Number
* Report: VerifEye - All Alarm Verifications
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Ranking Type: Location
* Max items displayed: Ex. 10
* Ranking order: Descending
* Name: “VerifEye - False Alarm - No person detected”
* Tag: “Alarms”
### Employee Result: Location Ranking
Rank locations based on the number of "Employee" false alarms.
**Widget Configuration Settings:**
* Widget Type: Ranking
* Graph Type: Number
* Report: VerifEye - False Alarm - Employee
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Ranking Type: Location
* Max items displayed: Ex. 10
* Ranking order: Descending
* Name: “Top 10 Locations - Employee”
* Tag: “Alarms”
### Person in Public Area: Location Ranking
Rank locations by "Person in Public Area" detections.
**Widget Configuration Settings:**
* Widget Type: Ranking
* Graph Type: Number
* Report: VerifEye - False Alarm - Person in public area
* Category: Other
* DataType: Bookmarks (Count)
* Statistic: Count
* Ranking Type: Location
* Max items displayed: Ex. 10
* Ranking order: Descending
* Name: “Top 10 Locations - Person in public area”
* Tag: “Alarms”
---
# 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.solink.com/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-widgets-guide.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.