> 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/categories.md).
# Categories
Categories allows you to categorise reports and keeps them organized.
## Creating Categories
To create a category, follow the steps below:
{% stepper %}
{% step %}
### Go to Site Settings > Categories
Under the Site Settings tab, select the **Categories** section.
{% endstep %}
{% step %}
### Click 'Create Category' to create a category
Click the **'Create Category'** button to create a category. Your newly-created category should appear at the bottom of the list.
{% endstep %}
{% endstepper %}
Please note that a category is required for all reports. By default, Kitehouse gives you most of the categories that you may encounter.
***
## Editing Categories
To edit a category, simply click the category you'd like to edit and a menu pops out.
In the menu, you are able to change the colour of the category and it's name. Be sure to hit **Save** to save your changes.
***
## Deleting Categories
To delete a category, simply click the 3 circles on the category you would like to delete and click **Delete 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/categories.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.
.png?alt=media&token=954afea6-7984-47f0-8b6c-3a54c97efbbc)
.png?alt=media&token=6503863d-8e7d-445d-8f79-d06ee2dfd0d5)