> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/enterprise-features/priority-level.md).
# Priority Level
{% hint style="info" %}
This feature is currently only available on demand for Enterprise customers.
{% endhint %}
Priority Level Grid button
The Priority Level feature allows you to adjust the priority of your assets in the queue.
{% embed url="" %}
Learn how to use the Priority feature
{% endembed %}
In the Priority Level grid view, you can designate assets as urgent or high priority directly from the Assets page, ensuring critical items are processed first.
To change an asset's priority, drag and drop the asset into your desired priority level. A popup confirmation will appear to ensure you'd like to change the priority level.
{% hint style="warning" %}
Please note that **you cannot downgrade an asset's priority level**, and **you can only upgrade an asset's priority level once**.
{% endhint %}
In the grid view, you can also click the quality tag to open a dropdown menu, allowing you to adjust the priority level of the processing asset.
---
# 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://docs.kaedim3d.com/enterprise-features/priority-level.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.
