> ## Documentation Index > Fetch the complete documentation index at: https://docsy3.mile.app/llms.txt > Use this file to discover all available pages before exploring further. # Alert Setting > Choose which alerts are recorded, which ones also send a notification, and the limit that raises each one. **Alert Setting** decides, for each type of alert, whether it is recorded at all, whether it also goes to the notification bell, and the limit that raises it. It applies to the whole organization. Open **Settings › Alert Setting**. > [!NOTE] > > Required permission: > > * View alert setting > * Edit alert setting Without **Edit alert setting** you can see the settings, but the switches and limit fields are locked and the page says *Only an admin can change this*. ![Alert Setting](https://mintcdn.com/mile-app/WPibWyW63U4l5gcF/images/v4/settings/alert-setting.png?fit=max\&auto=format\&n=WPibWyW63U4l5gcF\&q=85\&s=529f5ac9a68c20339f942b9f738daaf6) The line at the top reminds you who receives alerts: *Alerts are sent to every role with the View alert permission.* To change who gets them, turn **View alert** on or off for a role in [Permission](https://docsy3.mile.app/pages/settings/permission/introduction.md). ## Alert types and limits Each row shows the alert type and one sentence that says when it is raised, using your organization's current limit. Under the sentence are the fields for that limit. | Alert | Sentence on the page (with the default limits) | Limit you can change | Allowed range | Default | | - | - | - | - | - | | **Geofence** | *When a driver enters or leaves a geofence* | None. See [Geofence](https://docsy3.mile.app/pages/settings/geofence.md). | | | | **Idle** | *When a driver moves less than 50 m within 30 min* | **Distance** and **Within** | 10–1000 m and 5–120 min | 50 m within 30 min | | **Lateness** | *When a task is predicted to arrive more than 2 min late* | **Grace period** | 0–60 min | 2 min | | **Route deviation** | *When a driver goes more than 150 m off the planned route* | **Distance from route** | 76–2000 m | 150 m | | **Overspeed** | *When a driver drives faster than 80 km/h* | **Speed limit** | 20–200 km/h | 80 km/h | | **Low battery** | *When a driver's phone battery drops to 15% or below* | **Battery at or below** | 2–60 % | 15 % | | **Driver offline** | *When a driver on a trip sends no location for more than 30 min* | **No location for** | 10–120 min | 30 min | An organization that never changes a limit keeps the defaults. Some parts of the rules are fixed and cannot be changed: * **Route deviation** and **Overspeed** need 3 location updates in a row beyond the limit before an alert is raised. * **Idle** and **Overspeed** alerts are repeated every 10 minutes while the driver is still idle or still speeding. * **Low battery** alerts are repeated every 30 minutes while the battery stays at or below the limit. * **Driver offline** raises one alert each time a driver goes silent. It is not repeated while the driver stays offline. Overspeed, Low battery and Driver offline are off until you turn them on. See [Overspeed](https://docsy3.mile.app/pages/monitoring/alert.md#overspeed), [Low battery](https://docsy3.mile.app/pages/monitoring/alert.md#low-battery) and [Driver offline](https://docsy3.mile.app/pages/monitoring/alert.md#driver-offline) for when they are raised and when they stop. ![Low battery row in Alert Setting](https://mintcdn.com/mile-app/UXNIt6vKEPCdUxjB/images/14zp1phc071_v4alert-add-low-battery-alert/alert-setting-low-battery.png?fit=max\&auto=format\&n=UXNIt6vKEPCdUxjB\&q=85\&s=604c41fcd42a282cd8a2c2143b73fcd6) ![Driver offline row in Alert Setting](https://mintcdn.com/mile-app/UXNIt6vKEPCdUxjB/images/14zp1phc072_v4alert-add-driver-offline-alert/alert-setting-driver-offline.png?fit=max\&auto=format\&n=UXNIt6vKEPCdUxjB\&q=85\&s=d55583724fe04244567a9633e218fa4e) ### Change a limit 1. Type the new value in the field, for example **Speed limit** under **Overspeed**. 2. Click outside the field or press **Enter**. The value is saved right away; there is no Save button. Each field is saved on its own. The sentence above the field updates to the new limit. * The value must be a whole number within the allowed range. Otherwise the field says, for example, *Enter a whole number from 20 to 200 km/h*, and nothing is saved. * If saving fails, the field goes back to the value that was saved before. A new limit applies to detections after it is saved. Alerts already recorded do not change. ## The switches The table lists each **Alert Type** with two switches. A change is saved as soon as you flip a switch; there is no Save button. | Column | On | Off | | - | - | - | | **Active** | The alert is recorded in [Alert](https://docsy3.mile.app/pages/monitoring/alert.md) history and shown in [Tracking](https://docsy3.mile.app/pages/monitoring/tracking/introduction.md). | New alerts of this type are not recorded. | | **Notification** | The alert is also sent to the notification bell. | The alert is still recorded and shown in [Tracking](https://docsy3.mile.app/pages/monitoring/tracking/introduction.md) and [Alert](https://docsy3.mile.app/pages/monitoring/alert.md) history, but no notification is sent. | Screen readers announce the **Active** switch as *Record* followed by the alert type, for example *Record Overspeed*. **Notification** follows **Active**: * Turning **Active** off also turns **Notification** off and locks it. * Turning **Active** on also turns **Notification** back on. Both switches are saved together. To keep an alert recorded without a notification, turn **Active** on first, then turn **Notification** off. Turning an alert off stops new alerts of that type. Alerts already recorded stay in **Monitoring › Alert**. You can change a limit while the alert is off; it applies once you turn the alert on. The line at the bottom shows who changed the setting last and when, for example *Last changed by Dewi Anggraini, 2 days ago*. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.