> 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/incident-forms.md).
# Incident Forms
Incident Forms allows you to add more information to an incident. This can be customised per incident category.
## Creating an Incident Form
To create an incident form, follow the steps below:
{% stepper %}
{% step %}
### Go to the Incident Form Tab
Under **Site Settings**, select the **Incident Form** tab.
{% endstep %}
{% step %}
### Click 'Create Form'
Click the 'Create Form' button to create a source label. Your newly-created label should appear at the bottom of the list.
{% endstep %}
{% endstepper %}
***
## Configuring your Form
To configure your form, simply click the form you would like to continue and a menu should pop out.
Simply select which categories will receieve the form and the fields where staff members can fill in information. You can select if they are required or not.
Once enabled, if a staff member created a report using the category you've assigned, your fields will be shown in the incident report.
---
# 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/incident-forms.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.
