> 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/settings/workflow.md). # Workflow Response phases and reusable task checklists. **Settings → Workflow** is where Administrators describe *how* your organization responds, so every incident does not start from a blank page. ## Response phases A workflow is a sequence of phases — for example Detected → Mitigating → Communicating → Resolved. You can keep one default workflow or create several (for example a security path and an availability path). On an incident, people record when each phase happened. Those marks become the response-time picture used in analytics. You can start from a template and then rename, add, or remove phases. Deleting a workflow archives it; incidents that already used it keep their history. An individual incident can also use a custom timeline. That change stays on that incident and does not rewrite the shared workflow. ## Action item templates Templates are reusable checklists (for example “customer communication” or “security incident first hour”). Give the template a name, add the steps, optionally tag it, and mark it active. On an incident, apply a template instead of typing the same tasks every time. Responders can still add or remove tasks for that specific 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/settings/workflow.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.