Automation — Rules
The "Automation" area is the hub for rule-based notifications and follow-up actions. Every rule follows the if-then pattern: a trigger (e.g. "Patrol missed"), optional conditions, and one or more actions. The rules overview shows at a glance which rules are active, who is notified, and via which channels.
Features Overview
Rules Table
Each row is a rule. Besides name and trigger, the table shows two key columns:
| Column | Content |
|---|---|
| Recipients | Who is notified — role and person badges |
| Channels | How they are notified — email, SMS, call, push, in-app |
Use the toggle in the row to enable or disable a rule without deleting it.
New Rule
The "New rule" button opens the workflow editor as a full page. There you build the rule graphically from trigger, conditions, and actions. Clicking an existing rule opens the same editor for editing.
Triggers
Rules can react to these events, among others:
- Patrol missed / completed
- Checkpoint missed
- Checkpoint scanned (with condition fields such as checkpoint, employee, and "photo present")
- Incident created / classified
- Form submitted, defect detected
- Shift start / shift end, missing check-in / check-out
- Employee absent for an extended period
- Proof-of-life overdue
Templates & Recipients
Use the tabs of the area to reach the notification templates (message texts with placeholders) and the recipients (account-based notification recipients).
Scope
By default, rules apply to the entire account. However, you can limit a rule to a single property or customer — either in the rule editor or directly in the property (Property → Automation, where only that property's rules appear).
Good to Know
:::tip Note
- The rules fully replace the former notification checkboxes in the property settings. Whatever was configured there (e.g. email on missed patrol) is now modeled as a rule.
- For new accounts, a set of sensible default rules is created automatically, which you can adapt or disable.
- The same event triggers a rule only once — even if data from the mobile app is synchronized multiple times, you will not receive duplicate notifications.
- If a notification fails (e.g. due to a connection issue), delivery is automatically retried several times.
- If a rule cannot determine any recipients (e.g. an empty role), this is visibly noted in the execution result — it does not get lost silently. :::
Permissions
:::info Permission To use this page, you need the View automation permission. Contact your administrator if you do not have access. :::
| Action | Permission |
|---|---|
| View rules | View automation |
| Create and edit rules | Create/edit automation |
| Manage templates and recipients | View settings |