> 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/understand-your-business/ai-features/compliance-analytics/blocked-exit-detection.md). # Blocked Exit Detection **Blocked Exit Detection** is a premium feature in Solink that allows you to receive a notification whenever an exit door is obstructed at your business. Many businesses in the U.S. are subject to costly OSHA fines whenever an exit door is obstructed. Blocked Exit Detection allows you to proactively address blocked exits to help reduce safety/health fines. Check out the following video and article for more information on how to set up and use Blocked Exit Detection: {% embed url="" %} **Note**: Blocked Exit Detection is available with a subscription to [Solink's AI Package](https://solink.com/lp/try-ai/). *** ## How it Works After you have configured Blocked Exit Detection (see [Configure Blocked Exit](#configure-blocked-exit-detection) detection below), you will receive an email and/or SMS text notification if there is an obstruction in the area you have specified. The following flow provides a high-level overview of how Blocked Exit Detection works: 1. Our Artificial Intelligence (AI) model checks the specified exit door for obstructions. 2. If there is an obstruction, a notification is sent via email/SMS and an event is created: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-bdd1ad02fe9e824f71433078ec201dec9b120161%2Fd8bd863222889374.png?alt=media) **Note**: The criteria that must be met for the creation of an obstruction event is: if an obstruction is present for 10+ minutes and the AI is 80% confident the objects detected are obstructions. See the following section for information on how to configure a blocked exit motion zone. *** ## Configure Blocked Exit Detection The first step to configure Blocked Exit Detection is to reach out to our Support team. Once a member of the team has enabled the feature on your account, you can configure a motion zone on **up to three cameras** to monitor an exit door for obstructions. ### Motion Zone Setup To configure a Blocked Exit Detection motion zone: 1. Select a camera from the **Video** page. 2. In the video player, select the "gear" icon > **Motion Zones**. 3. Select **Zone Type: Blocked Exit Alerts**: 4. Highlight the entire exit door and an area up to 3 feet in front of the door. This is ideally the area where you want to receive a notification whenever an object is obstructing the door: Take note of your camera placement in relation to the door as well, as this can affect the accuracy of Blocked Exit Detection. *** ## Recommended Camera Placement For optimal results with Blocked Exit Detection, follow the examples provided in the following images to ensure your cameras are placed in ideal locations: *Use cameras with a line of sight squarely facing the door and where shelves or stacked boxes will not obstruct the view of the exit area.* *Use cameras with a clear line of sight of the door and where shelves or stacked boxes will not obstruct the view of the exit area.* *Avoid using cameras where the line of sight to the door can be obstructed by objects outside of the exit area (e.g., shelves, stacked boxes).* *Avoid using cameras where the line of sight is perpendicular to the door making it difficult to distinguish the door.* *** ## Set Up Blocked Exit Notifications To ensure you receive notifications for Blocked Exit Detection whenever an exit is blocked, follow these steps: * [Create a report to track blocked exit events](#create-a-blocked-exit-report) * [Create a widget from the report](#create-blocked-exit-widget) * [Create a threshold widget](#create-blocked-exit-threshold-widget) **Note**: Reach out to your Solink Customer Success representative for assistance with these instructions if needed. ### Create a Blocked Exit Report 1. Navigate to the **Events** page > **All** tab. 2. Use the search bar to filter the events to only show **Blocked Exit** events. 3. Save the report. When creating the report, use a descriptive name like "Blocked Exits" so it is easy to find. ### Create Blocked Exit Widget 1. On the **Dashboard** page, select **+Widget**. 2. Choose the "Report" widget type. 3. Under **Select Data Set**, choose the "Blocked Exits" report you created. 4. Select the following options in the next steps: 1. **Category**: Other 2. **Data Type**: Bookmark 3. **Statistic**: Count 4. **Locations**: Select the desired locations where you want to track blocked exits. 5. Above the graph on the right side of the widget creator, select **Use a rolling time frame** to monitor the past seven days of data. 5. Type a name for the widget in **General Widget Settings**. 6. Select **Create Widget** to create the widget. ### Create Blocked Exit Threshold Widget 1. On the **Dashboard** page, select the more actions icon (three dots) for the widget you created, then select **Create Threshold:** ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-09de3dd5fd97f16aa360c01b651c535024fcabac%2F527324ec9044ba4c.png?alt=media) 2. Select **Absolute** for the **Threshold Value**. 3. Set the Absolute value to a number that when exceeded will send you a notification (how many blocked exit events must have occurred to receive a notification). 4. Select Trigger notification when data is = **Above.** 5. Choose how you would like to be notified (e.g., SMS and/or Email). 6. Select **Save** to create the threshold widget. You will be notified when there is a blocked exit in the future. *** ## How to Review Blocked Exit Events To review your Blocked Exit events: 1. Select the **AI** tab near the top of the **Events** page: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-fda653af1afd1e78a44380b46b6d2a241f289ff5%2F57378874431ba603.png?alt=media) 2. Select **Blocked Exits** near the top-right of the Events page: Any Blocked Exit events appear on the Events page once you have filtered according to the steps listed above. *** ## Blocked Exit Detection FAQs **Q: How do I receive notifications for blocked exit events?** A: See [Set Up Blocked Exit Notifications](#set-up-blocked-exit-notifications). **Q: How many cameras can I run this feature on at each location?** A: Blocked Exit Detection can be run on **3 cameras per location**. Attempting to configure more cameras for a single location may introduce performance issues. **Q: Can I control which employees have the ability to modify a blocked exit motion zone?** A: Yes - contact our [Support](/docs/get-started/introductory-guides/how-to-contact-our-team.md#phone) team to assign an additional employee to create/modify motion zones. **Q: Which camera types is this feature compatible with?** A: Nearly all camera types except thermal and 360 cameras are supported. **Q: Can blocked exit checks be scheduled and/or paused during certain times of the day?** A: No, blocked exit events cannot be scheduled - however, they can be delayed for a given period of time after the last obstruction event. Please contact [Solink Support](/docs/get-started/introductory-guides/how-to-contact-our-team.md#phone) to adjust the time between events. *** ## Additional Notes Please take note of the following caveats regarding Blocked Exit Detection: * Glass and sliding doors are currently not compatible with Blocked Exit Detection. * You can have **up to three cameras per location** with Blocked Exit Detection. * You can create **one blocked exit motion zone per camera**. * You currently cannot configure blocked exit motion zones in the Solink mobile app. --- # 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/understand-your-business/ai-features/compliance-analytics/blocked-exit-detection.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.