> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/features/email-notifications/daily-summary-email.md). # Daily Summary Email The notifications are for the user making the change. (i.e. you can’t set notification preferences on behalf of someone) You are setting the preferences for yourself. When an issue is detected it is determined by the downtime threshold. The email is sent as soon as an issue (station inactivity) is detected. The downtime threshold is set in Admin > Station (select which one) > Edit. If Utilisation is selected (in Downtime Detection mode) the Utilisation Downtime Threshold (mins) should be set to when you want to receive a notification after how many minutes of downtime. Escalated issues are when the operator presses a button on the tablet. There are no changes in the stations Admin required to receive emails. #### Benefits These emails are helpful in prompting managers to take action on the previous day's downtime. Also delivering key data to a wider group who may not access Busroot on a daily basis. #### Setup Stations must be configured to either Production Cycle monitoring, Utilisation Monitoring or Independent Process Speed. Each user to receive the email should set which data they want to receive. This can be done under Notification Preference in the main menu and set at Station Group level. #### Daily Workflow 1. At 7:00am Busroot sends out the Daily Summary email to selected users, containing a summary of downtime from the previous day. 2. The whole management team is kept up to date with what's happening on the shop floor. Issues can be discussed in meetings to find solutions, any changes or improvements can be easily monitored. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.output.industries/features/email-notifications/daily-summary-email.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.