> ## Documentation Index > Fetch the complete documentation index at: https://docs.ctechnology.io/llms.txt > Use this file to discover all available pages before exploring further. # Notifications > Notify your team when something happens to a selection of your vehicles, by web, app and email. The **Notifications** section lets your organization define rules once and have the right people on your team informed when something happens to your vehicles. Instead of every team member configuring every vehicle, you describe the event, the vehicles and the recipients in one place. Notification rules of an organization are separate from the personal notification rules that every user can set up for a single vehicle, which are described in [Notifications and alerts](/handbook/private/notifications). Personal rules are not affected. > [!NOTE] > > The section is available to organizations that have notification rules enabled. Which team members can see and change rules depends on their role, see [Who can see and edit rules](#who-can-see-and-edit-rules). ## What a notification rule is A notification rule combines four things: * **A trigger**, the event the rule reacts to, for example "Battery level below 20 %" or "Fault code reported". * **The vehicles** the rule watches. The selection stays current by itself: new vehicles that match are included automatically. * **The recipients**, up to 25 team members, and for each person the channels they are notified through. * **Settings** such as the priority, a cooldown, an optional time window and whether the rule is active. The overview lists all rules of your organization with their name, trigger, the vehicles they apply to, the number of recipients, their status (active or paused) and the time of the last change. You can search the list and filter it by trigger. ## Triggers The trigger is chosen in the first step of the editor. The triggers are grouped as in the app. **Telemetry thresholds** react when a measured value falls below or rises above a threshold you set: * Battery voltage * Battery level * Fuel level * Temperature * Distance from home **Vehicle events** react when something happens to a vehicle. They need no further settings: * Ignition switched on * Ignition switched off * Vehicle starts moving * Vehicle towed or tilted * Device power disconnected * Battery low * Vehicle offline * Arrived home * Left home * Shore power disconnected * Shore power connected * Put into the water * Taken out of the water * Range critical * Fuel not full on return **Fault codes** react when a fault code is reported for a vehicle. You can choose a minimum severity, or react to any severity. **Maintenance** reacts when a maintenance task becomes due soon or overdue, whether it is due by time, distance or operating hours. **Geofences** react when a vehicle enters or leaves one of your organization's geofences, see [Geofence rules](#geofence-rules). For a threshold trigger, choose the condition ("Falls below" or "Rises above") and the threshold value. The rule notifies when the value crosses the threshold, not on every update while it stays beyond it. ## Geofence rules A geofence rule notifies your team when a vehicle enters ("Geofence entered") or leaves ("Geofence left") one of your organization's geofences. * **One geofence per rule.** In the editor you choose the geofence the rule watches. The picker is available to team members who may see the organization's geofences. * **Vehicles.** The rule applies to the vehicles of that geofence, shown as "All vehicles of the geofence". In the vehicles step you can narrow this to a subset, for example one vehicle type. The editor then shows how many vehicles are covered, for example "3 of 12 vehicles". A rule never covers vehicles the geofence does not apply to. * **Once per crossing.** Each entry or exit is reported once per vehicle, however many rules or recipients there are. The default cooldown is 5 minutes, so a vehicle moving along the edge of a geofence does not flood your team. Priority, time window and channels work as for every other rule. * **Who is notified.** Only team members who may see the organization's geofences and where the vehicle is receive the notification. Members who may not are marked "May not see the geofences" and must be removed before you can save the rule. * **Deleting a geofence.** When you delete a geofence, the rules that use it are switched off, not deleted. The delete dialog tells you how many rules are affected. Such a rule is marked "Geofence deleted" and can only be switched on again after you choose a geofence that still exists. The entries and exits also appear in the vehicle logbook. ## Choosing vehicles In the second step you choose which vehicles the rule applies to: * **All vehicles** of your organization. * **A vehicle category**, **family** or **type**. * **Chosen vehicles**, a selection you pick one by one. The editor shows the effective vehicle count next to the selection, so you can see how many vehicles the rule currently covers. Because the selection is kept up to date automatically, a rule for a category also covers vehicles that join the category later. ## Expected notifications and the noisy rule warning Next to the vehicle selection, the editor shows an estimate under **Expected notifications**: about how many notifications a day each recipient will receive, based on the trigger, the number of vehicles and the cooldown. Triggers without an estimate show "No estimate for this trigger yet." If a rule is likely to produce a flood of notifications, a warning appears, for example "This rule may create about 400 notifications a day for each recipient (100 vehicles × about 4 per vehicle and day)". The warning also appears in the summary and as an icon in the overview. There is no hard limit: you can still save the rule, for example because a large fleet with a frequent trigger is intended. To reduce the volume, select fewer vehicles, choose a longer cooldown, restrict the rule to a time window or pick a less frequent trigger. ## Recipients and channels In the third step, choose the team members who are notified, up to 25 per rule. Only members who have access to the organization can be selected. Members without access are marked "No access to the organization" and must be removed before you can save. For each recipient you choose the channels: | Channel | What it does | | - | - | | **History** | Every notification is always kept in the person's notification history. This cannot be switched off. | | **Web** | A notification in the web application. | | **App** | A push notification on the person's mobile device. | | **Email** | An email. | Emails are bundled: a person receives at most one email from your organization every 5 minutes, listing everything that happened in between. The email carries your organization's name and logo and offers an unsubscribe link for each rule. When a recipient unsubscribes from the emails of a rule, the editor shows "Unsubscribed on" for that person and you cannot switch the emails back on for them. Only the recipient can do that, see [Notifications and alerts](/handbook/private/notifications#organization-notifications). Until you add team members, nobody is notified by the rule. If a team member is removed from your organization, they no longer receive notifications from your rules. ## Settings The first step also holds the settings of the rule: * **Name** and an optional **description**. The name is shown to recipients as the title of the notification. * **Notification priority**: Low, High or Alert. High and Alert also show a pop-up to recipients who are using the web app. * **Cooldown**: the shortest time between two notifications of this rule for the same vehicle. You can keep the default of the trigger (shown in brackets), choose no cooldown, or choose a duration from one minute up to seven days. * **Only within a time window**: notify only between a start and an end time of the day, in a time zone you choose. A start later than the end wraps past midnight, for example 22:00 to 06:00. * **Active**: a paused rule keeps its settings but notifies nobody. A summary of the rule is shown before you save it. ## Creating, editing and deleting rules Click **New notification rule** to open the editor. It guides you through three steps, **Trigger**, **Vehicles** and **Recipients**, followed by a summary. Any problem, such as a missing name or threshold, is shown with a short message before you can continue. Use the edit icon in the overview to change a rule and the trash can icon to delete it. Deleting asks for confirmation. A deleted rule stops notifying immediately, and the notifications it already created stay in the recipients' histories. To stop a rule temporarily without losing its settings, pause it instead of deleting it. ## Who can see and edit rules * Team members with the **view** permission see the Notifications section and the list of rules. * Team members with the **edit** permission can also create, change and delete rules. * Administrators, standard, service, marketing and engineering users can view and edit. Read-only users can view only. Receiving notifications does not need either permission: any team member with access to the organization can be chosen as a recipient. For the roles of your team, see [Team management](/handbook/oem/team). > [!NOTE] > > The vehicle events created by thresholds of your organization are visible only to members of your organization. Vehicle owners and other organizations that also hold the vehicle do not see them. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.