Recipients & Contacts
Under Tools → Automation → Recipients & Contacts you can see how your employees and customers can be reached. The page answers the question "Will a notification actually arrive?" — before a rule runs into a dead end in an emergency.
What Is This View For?
Automation rules send notifications to roles, properties, or individual people. Whether the message arrives depends on the master data: no email address means no email, no phone number means no SMS and no call. This overview shows the contact details of employees and customers together and highlights missing entries so you can close the gaps.
You edit the contact details directly here — they are stored in the master data of the respective employee or customer. There is no separate recipient management.
Moved
The former page with saved notification recipients has been removed. Today you select recipients directly in the rule (see below); old bookmarks redirect to the rules overview.
Recipient Types in the Rule Editor
In the rule editor you define per notification who receives it:
| Recipient type | Who is notified |
|---|---|
| Role | All employees with a specific role |
| Specific person | Individually selected people |
| Fixed recipients | Email addresses or numbers entered directly in the rule |
| Object role | Employees with this role who are assigned to the affected property |
| Property assignees | All people assigned to the affected property |
| Property notification emails | The notification addresses stored on the property |
| Phone book (all account numbers) | All phone numbers stored in the account |
| Attendance config numbers | The numbers stored in the shift preset |
| Attendance configuration emails | The addresses stored in the shift preset |
| Task assignee | For task triggers: the assigned person |
| Today's shift staffing | For shift triggers: the people planned as staffing of the shift today (planning staffing) |
| Person from the event | The person affected by the event — e.g. the assigned person for "Shift assigned/changed" or the reporting person for "Sick report decided" |
| Absence deciders | For sick-report triggers: the people allowed to decide this person's report (permission "Edit time tracking" or administrator) who are responsible for all properties or for one of the person's properties — if nobody matches, the "First admin" role |
| Customer contacts | The contacts of the customer the affected property belongs to (customer view → Contacts), provided an email address is stored — e.g. for the completion proof of a task. If the property has no customer, nobody is notified |
Contact details are always read live from the master data — if a phone number changes, all rules are automatically up to date.
If a rule finds no reachable recipient, the rule history (Activity log, source "Rules") shows "No recipients" in the detail line of the execution; the reason appears in the execution details after clicking the row. Exactly these cases are what you resolve on this page.
Permissions
| Action | Required permission |
|---|---|
| View contact details | View employees or View customers |
| Edit employee contact details | Edit employees |
| Edit customer contact details | Edit customers |