> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.flowace.ai/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Late Logout Alert ${youtube}[Late Logout Alert in Flowace: How to Set It Up (Step-by-Step)](0qg-mWuuE7Y) --- **Alert type:** Attendance **Schedule:** Daily/Weekly Notification **Available on:** Basic and above **Who can set it up:** Workspace Admin Where to find it: **Admin Settings › Alerts** The Late Logout alert tells which members were still working after an agreed time. It shows where long days are repeating, so you can talk about workload and rest while it matters. --- ### When to use this alert Working late is sometimes planned, for a release, a client deadline or an incident. When it repeats, it can point to workload or planning issues, and for teams with set hours it can raise overtime questions. This alert sends the names to the right people the same evening. **Use it to:** * Notice late finishes on the evening they happen. * Apply one end-of-day cut-off consistently across a team. * Give managers and HR the same list without anyone compiling it by hand --- ### Example alert setup | End Time is greater than equals a Custom value of 08:00 PM, on Monday to Friday. | Field | Value | | ---- | ---- | | Alert Schedule | Daily Notification | | Alert Type | Attendance | | Alert Name | Late Logout (Customer Support) | | Variable | End Time | | Condition | greater than equals | | Compare With | Custom | | By | 08:00 PM | | Apply alert on | Custom: Monday to Friday | | Whom to monitor | Individual members, teams or the entire organization. In this example: the Customer Support team. | | Who gets notified | Individual, Reporting Manager, All Admin, Custom | | When to send | Same day at 08:30 pm | **Note: All values in this article are examples.** Times, hours and percentages are sample values to help you get started. Adjust them to your own working hours, roles and policies. They are not benchmarks or recommendations for any industry. --- ### How to set it up 1. Open the alert settings: go to **Admin Settings › Alerts.** 2. Click **"Create New"** button 3. Choose the **Alert Schedule**: Daily Notification. 4. Set the **Alert Type** to Attendance and enter an **Alert Name**, for example "Late Logout (Customer Support). 5. **Set the condition:** * **Variable:** End Time * **Condition:** greater than equals * **Compare With:** Custom * **By:** 08:00 PM 6. Choose **Apply alert on**: Custom, then select Monday to Friday. 7. Choose whom to monitor: under **Applicable to**, select Teams, then choose Customer Support. 8. Choose **who gets notified**: Individual, Reporting Manager, All Admin, Custom 9. Set **when to send**: Same day at 08:30 pm. 10. **Save the alert** and activate it. ![](https://storage.crisp.chat/users/helpdesk/website/-/6/7/1/e/671eefeed0317800/image_2qqyz5.png) --- ### How the rule is evaluated **End Time** is the time a member's day ends . Because the condition is greater than equals, an end at exactly 08:00 PM also triggers the alert. In plain English: the alert lists every member of Customer Support whose day ended at 08:00 PM or later. Set the value to the team's end time plus the margin you want to allow. For a 07:00 PM finish and a one-hour margin, use 08:00 PM. Once a member's End Time reaches the value, it stays at or above it, so the list is reliable from 08:00 PM. The End Time shown is the time recorded when the alert runs: a member still working at 09:00 pm appears with the End Time recorded up to that point, not their final finish. **Worked example** Rule: End Time is greater than equals 08:00 PM. | Member | End Time | Triggers? | | ---- | ---- | ---- | | Priya Sharma | 06:58 PM | No | | Karan Malhotra | 07:40 PM | No | | Rohan Mehta | 08:00 PM | Yes (equals the value) | | Ananya Iyer | 08:35 PM | Yes | | Sneha Kulkarni | 08:50 PM | Yes | --- --- ### What recipients receive Recipients receive an email naming the members who met the condition. ``` Dear User, Please be informed that the 'Late Logout (Customer Support Team)' alert has been triggered. Currently, 10 out of 50 users have met the following criteria(s): End Time is greater than or equal to custom value of 08:00 PM For a comprehensive view, please refer to the attached CSV file with detailed information. You can adjust the alert settings here. We hope this information assists you in identifying trends, making informed adjustments, and supporting a balanced, productive environment for your team. Best regards, Flowace Team ``` | Download the sample csv: http://de9j6rhbdgsa2.cloudfront.net/sample-reports/late-logout-alert-sample.csv --- ### Choosing recipients and timing | Field | Recommendation | Why | | ---- | ---- | ---- | | Who gets notified | Reporting Manager, Custom | The manager can check workload; HR sees the pattern. Individual is left out by default; add it if you want members to see the same prompt. | | When to send | Same day, 08:30 pm | An hour after the cut-off, so members who finish shortly after 08:00 PM are recorded. | | Apply alert on | Monday to Friday | The team's working week. Add other days only if you want to review work on them. | **Use this alert as a prompt for a conversation.** Late Logout shows a pattern worth checking; it does not explain why it happened. Tell your team which alerts exist and why, send the alert only to the people who need to act on it, and look at the pattern over several days before drawing conclusions. --- ### Reading the results: common scenarios | What you see | What it may mean | What to do | | ---- | ---- | ---- | | One member listed once | A planned late finish, such as a release or deadline | Usually no action; note the pattern. | | The same member on several days | A workload that does not fit the day, or a routine moving later | Check in about workload and rest. | | Several members on one day | A shared deadline or incident | Check the cause and plan the workload | --- ### Good to know * **Choose the day carefully.** If every day of the week is selected, the alert also runs on weekends and holidays for everyone who was not working. * **Values are per team or role**. Different teams work different hours; set a separate alert for each. * **Alerts follow your workspace settings.** Working days and the time zone configured for your workspace decide when an alert runs. * **Choose the margin to suit the team.** A narrow margin fires often; a wider one lists only clear late finishes. --- ### FAQs * **Are the values in this article fixed?** No. The times, days and recipients in this article are examples. Change **By**, **Apply alert on**, **Whom to monitor**, **Who gets notified** and **When to send** to match your company's working hours and policies, and edit them whenever your policies change. * **Does an end at exactly the value I set trigger the alert?** Yes. The condition is greater than equals, so an end at exactly the value is included. * **Why does the email show an End Time earlier than the member's final finish?** The alert reports the End Time recorded when it runs, and a member still working continues beyond it. * **Why was a member who worked late not listed?** Check that the day is selected under Apply alert on, that the member is within Whom to monitor, and that an end time was recorded. * **Can I send it to the member only?** Yes. Select only Individual under Who gets notified. * **Can more than one person receive the alert?** Yes. You can select several options under **Who gets notified**, and Custom lets you choose specific people. --- ### Related articles [How to Set Up Custom Alerts in Flowace](https://help.flowace.ai/en/article/how-to-set-up-custom-alerts-in-flowace-v4qm3m/) **Need more help?** Reach out to support@flowace.ai and our team will be happy to assist. --- © Flowace Technologies Pvt Ltd | flowace.ai