> For the complete documentation index, see [llms.txt](https://kitehouse.co.uk/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kitehouse.co.uk/docs/admin/settings/status-pipeline.md).
# Status Pipeline
Status Pipeline allows you to track the current status of an incident. Each category can have it's own different pipeline and override the default.
## Configuring Default Status Pipeline
To create a status pipeline, follow the steps below:
{% stepper %}
{% step %}
### Go to the Status Pipeline tab
Simply head over to **Site Settings** then select the **Status Pipeline** section.
{% endstep %}
{% step %}
### Configure the Default Status Pipeline
The first section you'll see is the status pipeline for default incidents. All incident categories without a custom pipeline will use this.\
\
You can add/move/remove the different statuses and select which of them are terminal.\
\
To change the colour, simply click the coloured square and the available colours should appear below.
{% hint style="info" %}
A **Terminal** marks the end of the pipeline. You can select multiple statuses to be the terminal and staff members can simply select from a dropdown the desired status.
{% endhint %}
{% endstep %}
{% endstepper %}
***
## Category Overrides
Optionally, you can toggle a custom pipeline for categories that need different statuses than the default one. Simply tick the **Custom Outline** and customise the pipeline to suit your specific category.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://kitehouse.co.uk/docs/admin/settings/status-pipeline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
