This article explains which e-mail and in-app notification the preparation and return flow sends to whom and when, what waits during the night and how you choose your own notification preferences. The last section lists the flow's webhook events for those who want to connect the tasks to their own IT system. Every user chooses their own preferences; HR sets the sending time, the daily summary and the day of the missing items warning in General settings.
Before you start
The preparation and return flow is on (Setting up the preparation and return flow).
In the General settings > Notifications group, At what time are tasks sent?, Send a daily summary e-mail? and How many days before the start should missing items be flagged? are set.
Who gets what
When | Who | In-app notification | |
A task opened | The task's responsible people | Tasks opened for one person in the same flow are grouped in one e-mail; a task whose item has its own e-mail goes on its own | New preparation task or New return task |
A task was handed to you or you were added as responsible | The new responsible person | Yes | A task was handed to you |
A comment was written on a task | The task's responsible people and the flow's HR owner (not the writer) | No | New comment |
A reminder day came | The responsible people; only the one who took the task, if someone did | Yes | Reminder |
A task is late | The person in the item's Tell a manager setting; for a Critical exit task, the responsible person's manager | Yes, at once | A task is late |
The start date or last working day changed | The responsible people of open and planned tasks | Yes; several changes made within a short time go in one e-mail with the last date | The date changed |
Tasks or the flow were cancelled | The responsible people of the cancelled tasks | Yes, with the reason | Tasks cancelled |
The flow was cancelled after some work was done | The person who did the work and the flow's HR owner | Yes | Finished work may need undoing or Closed access may need reopening |
A working day morning | Every responsible person with work in the coming days | Daily summary | None |
The start is close and items are missing | The flow's HR owner and the employee's manager | Yes, at once | Items missing before the start |
Someone joins or leaves the team | The employee's manager | Yes, once per flow | Someone joins your team or Someone leaves your team |
The last working day passed and an asset was not returned | The flow's HR owner (with values) and the manager (without values) | Once a week | Assets not returned |
An outside person declined a task | The flow's HR owner | No | An outside person declined a task |
The flow's HR owner is the HR owner chosen in the extra task template; if the template has none, it is the person who started the flow. The notifications about deduction proposals are in Returns and closing access on leaving.
Details
Grouped e-mail: it goes out shortly after the tasks open; tasks opened at the same time go in the same e-mail. If a task is completed or cancelled before the e-mail goes out, it drops out of the e-mail; if no open task is left, no e-mail is sent.
Outside person: someone without a Teamso account gets no in-app notifications. They get a separate e-mail with the task link for each task; reminders, date changes and cancellations also come by e-mail. The e-mail is in the language of the flow's HR owner.
Reminder: it goes out on the item's reminder days after the general sending time. If the item has no reminders, one reminder goes on the due date. HR can also remind by hand on the Preparation and returns screen (Following preparation and returns).
Late task: with Tell a manager on in the item, the report goes out the chosen number of days after the due date; for a Critical task, as soon as the due date passes. For a responsible person without a manager or an outside e-mail address, HR is told. A task is reported once.
Daily summary: with Send a daily summary e-mail? on, it goes out on working days after the sending time. Each responsible person sees their open tasks due within the next six days or already late and the tasks that open within a week. Someone with no work gets no summary.
Items missing before the start: when the days left to the start reach the number in How many days before the start should missing items be flagged? (2 by default) or fewer, it goes once per flow for items still open or waiting. If the flow opened on the same day, the warning comes the next morning.
Notice to the manager: for records whose start date is in the past, the manager gets no joining notice.
Quiet hours
Between 21:00 and 07:00 no e-mail is sent unless it is urgent or critical; an e-mail created in these hours goes the next morning at the company's sending time (not before 07:00). In-app notifications always come at once. These e-mails do not wait for the quiet hours to end: tasks opened as urgent shortly before the start, critical tasks, late task reports, the missing items warning, the unreturned asset warning and a link sent again to an outside person.
Notification preferences
Click your name at the top right and open Notification settings (Notifications).
On the App notifications tab, the Onboarding group has these lines; choose for each whether it comes to the bell and to your phone:
Preparation and return: task opened, handed to you, new comment
Preparation and return: reminder
Preparation and return: date changed or cancelled
Preparation and return: daily summary
Preparation and return: someone joins or leaves your team
The Preparation and return: critical alerts line has no switch; it says Critical alerts cannot be switched off.
You can switch off the e-mails of the same types on the Emails tab under Workflow notifications.
Critical alerts report a late task, items missing for the first day and an asset that was not returned. If they were switched off, a new employee could start without a computer or a leaver's asset could be forgotten; that is why the e-mails and notifications about late tasks, missing items and unreturned assets always go out. E-mails to outside people have no preference either.
Connecting your own system: webhook events
On the Connect the tasks to your own IT system card in General settings, click Integrations; Company Settings > Integrations opens. Add the target address with Add Webhook and choose the events you want below in the Events field (Integrations and webhooks).
Event | When it is sent |
Preparation or return task opened | When a task opens for its responsible people (separately for each task); a planned task is sent when its opening day comes |
Preparation or return task completed | When a task is completed, with the value it wrote (for example the work e-mail) |
Onboarding date changed | When a new employee's start date changes; task dates move too |
Onboarding flow cancelled | When a new employee's whole preparation flow is cancelled |
Onboarding flow restarted | When a cancelled preparation flow is restarted |
Offboarding date changed | When a leaving employee's last working day changes |
Offboarding flow cancelled | When a leaving employee's whole return flow is cancelled |
Offboarding flow restarted | When a cancelled return flow is restarted |
The events carry work details only: the flow, task, item, category, responsible people, dates and the work value the task wrote. Pay, identity numbers, addresses, health data, the exit reason, asset values and driving licence details are never sent in any event. For an employee being hired or leaving, the existing Employee Hired and Employee Terminated events are used.
Example: if your IT team works in its own ticket system, connect the Preparation or return task opened event to it; every computer or e-mail task then opens there as a ticket. The Preparation or return task completed event reports back the work e-mail written when the task closes in Teamso. Try the connection with Send Test and follow the result in the Delivery Log.
Result
Responsible people learn about their tasks through a grouped e-mail and a notification; ordinary e-mails created at night go out in the morning.
Critical alerts always go out; everyone can switch off the other notifications for themselves.
The system you connect with a webhook hears when a task opens and closes, and when a flow's date changes, it is cancelled or restarted.
Common problems
Symptom: A responsible person got several tasks in one e-mail.
Cause: Tasks opened for one person in the same flow are grouped in one e-mail.
Fix: If an item should go on its own, choose This item's own e-mail for it (Managing preparation and return items).
Symptom: The e-mail of a task opened in the evening came in the morning.
Cause: Between 21:00 and 07:00 no e-mail is sent unless it is urgent.
Fix: This is expected; the in-app notification comes at once.
Symptom: The daily summary does not come.
Cause: Send a daily summary e-mail? is off, the day is not a working day, you have no work in the coming days, or you switched the summary off on the Emails tab.
Fix: Check the setting and your own preferences.
Symptom: I cannot switch off critical alerts.
Cause: Late task, missing item and unreturned asset alerts cannot be switched off.
Fix: To stop the alert, complete the task, use Not needed if it is not needed, or decide about the unreturned asset.
Symptom: The task opened event did not reach the webhook.
Cause: The task is still planned (its opening day has not come), the event is not chosen in the webhook, or the webhook is inactive.
Fix: Check the webhook's Events field and Active switch, and look at the Delivery Log.


