> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/management/notifications.md). # Incident notification contacts Who receives incident emails and how those messages are written. Under **Management → Incident notifications** you manage the people who should receive email when an incident needs to be communicated outward. ## Contacts For each contact you can store company, name, email, role, and whether they receive **individual** messages or are included in a **bulk** send. Add contacts before you need them. During an incident you should be choosing from a list, not typing addresses from memory. ## Email templates In the same area you can maintain templates: subject, body, sender name, and reply-to. Templates keep regulatory or customer updates consistent from one incident to the next. The incident’s **Notifications** section shows what was sent for that event. --- # 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://support.incidentlake.com/management/notifications.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.