> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/priorities/creating-a-priority.md).

# Creating a Priority

<mark style="background-color:yellow;">Step 1:</mark> From the **Priorities** module home page, click **Create Priority**.

<div align="left"><figure><img src="/files/qGKurMRc8NiiJJufEXEG" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 2:</mark>  Set the scope of the priority, and select what should be prioritized, *Assets* or *Findings.* Click **Add details**.

If client-specific priorities are enabled, select a client by scrolling through the list or using the search box to filter.&#x20;

<div align="left"><figure><img src="/files/qq3HJxhOYxxVJYEdk75c" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> Enter a priority name and additional information into the fields on the page.

<div align="left"><figure><img src="/files/SnPq7qcjeH1olP2ozEaz" alt="" width="554"><figcaption></figcaption></figure></div>

* **Priority name (required**): The title of the priority.&#x20;
* **Automatically add new recurring instances to this priority (optional):** Check this box if for every instance of an Asset or Finding, it will be brought into the priority automatically. This is recommended for a project whose scope might change.
* **Ignore information instances (optional):** Check this box if the priority excludes instances that do not contain a vulnerability.
* **Assignee(s) (optional):** Click the input field to select the assignee(s) for the priority.
* **Remediation owners (optional)**: A list of owner(s) who will own the priority remediation.&#x20;
* **Target remediation date (optional)**: Identifies the ideal date on which findings for the priority will be resolved. Place the cursor in the field box to select a date from the calendar.&#x20;
* **Description (optional):** An RTF field to enter a description of the priority.
* **Recommendation (optional)**: An RTF field to enter a recommendation for remediating the priority. A recommendation is the ideal advice or guidance to address a particular issue or concern. It suggests a best practice or a course of action to help prevent or mitigate security risks.
* **Remediation**: An RTF field to enter a remediation of the priority.&#x20;
* **Tags**: Enter any tags associated with the client (new or existing). Any special characters will be removed, and any spaces will be replaced with an underscore (\_).

<mark style="background-color:yellow;">Step 4:</mark> Click **Link assets.**

The information entered is presented on the priority details page.&#x20;

<div align="left"><figure><img src="/files/P8ux6d7kEEimAHEOvwnf" alt=""><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation/priorities/creating-a-priority.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
