> 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/priorities.md).
# Priorities
Priorities allows you to sort your incidents based on priority and can notify you which is needing immediate response.
## Creating a Priority Label
To create a priority label, follow the steps below:
{% stepper %}
{% step %}
### Go to the Priorities Tab
Under **Site Settings**, select the **Priorites** tab.
{% endstep %}
{% step %}
### Click 'Create Priority'
Click the 'Create Priority' button to create a priority label. Your newly-created priority label should appear at the bottom of the list.
{% endstep %}
{% endstepper %}
Please do note by default, Kitehouse will automatically create 5 categories to get you started.
***
## Editing a Priority Label
To edit a priority label, simply click the label you like to edit and a menu pops out.
In the menu, you can change the name and colour of the label and enable email notifications for site staff when the priority label is used.
To archive a label, simply click on the three dots on the side and click **Archive Priority**. Once archived, it will go to the **Archived** tab.
---
# 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/priorities.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.
