Holiday Emails

Flowtly Editorial Team2 min

Flowtly sends email notifications at every stage of the holiday request lifecycle. These emails keep employees and their approval chain informed without needing to check the app.

Holiday request created

When an employee submits a holiday request, each person in the approval chain receives an email with the request details. The email includes the requested dates, holiday type, and a link to review the request.

Holiday request submitted

The employee who submitted the request receives a confirmation email acknowledging that their request has been registered in the system.

Holiday request approved

When one approver in a multi-step chain approves the request, the employee receives an email indicating the approval and how many approvals remain before the request is fully accepted.

Holiday request accepted

Once all required approvals are complete, the employee receives a final acceptance email. This email includes a link to add the holiday to their calendar feed.

Holiday request rejected

If any approver rejects the request, the employee receives an email with the rejection reason provided by the approver.

Holiday added by manager

When a manager directly adds a holiday for an employee (bypassing the request flow), the employee receives a notification email with the holiday details and a calendar feed link.

Google Calendar sync error

If Flowtly encounters an error synchronising an approved holiday to Google Calendar, admin-level employees receive an error notification email so they can investigate.

Who receives what

Event Employee Approval chain Admins
Request created Yes
Request submitted Yes
Request approved Yes
Request accepted Yes
Request rejected Yes
Added by manager Yes
Calendar sync error Yes

Connection map

Refers toPart of
Documented hereDocumented elsewhere
audit-log records person. setting defines attribute. org-document access governed by setting. subscription gates setting.recordsdefinesaccess governed bygatesAAudit trail — The record of who did what and when. It is how a user action is investigated after the fact, and what compliance is demonstrated from.Audit trailPPerson — An employee. The central record the rest of the workforce data hangs off — profile, documents, leave, benefits, rates.PersonSSetting — Platform-wide configuration — behaviours, permissions, security.SettingAAttribute — A custom data field defined once and collected across the platform, so an organisation can record what Flowtly does not ship a field for.AttributeDDocument — An organisational file, stored with control over who can reach it.DocumentSSubscription — The plan the organisation is on, and what it is billed for.Subscription