> 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/review-events-and-save-evidence/events/motion-events/configure-motion-events.md).
# Configure Motion Events
Generate events when motion occurs in a specified area.
You can configure your cameras to create a motion event whenever they detect motion in a specified area (motion zone).
**Note**: Video alarms also look at motion to trigger alarms/events (see [Configure Motion Zones](/docs/protect-your-locations-with-alarms/alarm-setup/alarm-motion-zones.md) in the Alarm Setup section for more information).
To configure a motion zone:
1. Navigate to the **Video** page and select a camera.
2. Select the **Gear icon** > **Motion Zones**:
3. Ensure the **Highlight** button is selected.
4. Draw in the area where you wish to detect motion. When motion is detected in this area, a motion event is created.
**Note:** To avoid generating excessive motion events, try to select the minimum number of grid squares possible. For example, to detect motion when a door opens, only the top of the door needs to be highlighted in the region of interest (ROI) to generate an event.
5\. (Optional): Select the type of motion that triggers event creation:
* **Any Motion Alerts**: Any movement that occurs in the zone triggers event creation.
* **Blocked Exit Alerts**: Checks whether an object (such as a box, cart, or pallet) is blocking the exit door. It looks for a stationary object, not movement. Only available for users with the AI package. See [Blocked Exit Detection](/docs/understand-your-business/ai-features/compliance-analytics/blocked-exit-detection.md) for more information.
6\. (Optional) Set the motion sensitivity:
* **High (more alerts)**: Creates a motion event for small amounts of movement in the zone. Use it when you need to catch any activity, for example at a door that should stay closed after hours. Expect more events, including some from minor movement such as shadows or lighting changes.
* **Medium**: The default setting. It balances detection and event count, and suits most zones.
* **Low (fewer alerts)**: Creates a motion event only for larger amounts of movement. Use it in busy areas or areas with constant small motion, such as a shop floor or a window with passing traffic, to cut down on events you don't need.
7\. Select **Done** to save.
See the following section for more information on how you can track and visualize these events on the **Dashboard** page.
### Track Motion Events with Reports and Widgets
After you set up a motion zone, you can save a report of its motion events and display the report in a widget on the **Dashboard**. You can then see how often motion occurs, when it occurs, and where, without searching the **Events** page each time.
#### Step 1: Create a Motion Events Report
A report saves a search on the **Events** page so that you can use it again.
To create a motion events report:
1. On the **Events** page, select **Add Filter**.
2. Select the event type filter, then select **Motion**:
3. (Optional) Add a camera filter, and select only the cameras that have the motion zone you want to track. For example, select the back door camera:
4. (Optional) Add a time filter to show only the hours you care about, for example after closing time.
5. Select **Save Report**.
6. Enter a name that describes what the report tracks, for example "Back Door Motion: After Hours".
7. (Optional) Select a [notification](/docs/manage-users-locations-and-your-account/notifications.md) method: **Push**, **SMS**, **Daily**, or **Weekly**. With **Push** or **SMS**, you get a notification each time a motion event matches the report.
**Tip**: Create one report for each area that you want to track. Separate reports give you clearer widgets than one report for all cameras.
For more information, see [Create a Report](/docs/understand-your-business/search-and-save-reports/create-a-report.md).
#### Step 2: Add a Report Widget to the Dashboard
A Report widget shows the data from your report as a graph or a number.
To set up the widget:
1. On the **Dashboard**, add a [Report widget](/docs/understand-your-business/create-widgets/report-widget.md).
2. Under **Data Set**, select the motion events report that you created in step 1.
3. Under **Data Type**, select the motion events count. Under **Statistic**, select **Count**.
4. Under **Locations**, select the locations that have the motion zone.
5. Under **Time Frame**, select **Week** and select **Use rolling time frame**. The widget then always shows the last 7 days.
6. Select **Display Previous Time Frame Data** to compare this week with the previous week.
7. Under **Graph Type**, select **Bar graph** to see motion by day. To see only the total, select **Number**.
**Tip**: To find out when motion goes above a normal level, add a [threshold notification](/docs/understand-your-business/widget-configuration/threshold-notifications.md) to the widget. For example, you can get a notification when the back door has more than 20 motion events in a day.
### How Are Motion Events Different from Motion Search?
These are the differences between motion events and motion search:
* **Motion events** are created when a region of interest (ROI) is defined on a camera and motion is detected within that region.
* **Motion search** does not require a ROI to be set on a camera. You can conduct a motion search to check for instances of motion in a specific area of a camera. For more information, see [Motion Search](/docs/watch-and-find-video/video-tools/motion-search.md).
---
# 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/review-events-and-save-evidence/events/motion-events/configure-motion-events.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.