# Creating a Priority
Step 1: From the **Priorities** module home page, click **Create Priority**.
Step 2: If client-level priorities are enabled, select a client by scrolling through the list or using the search box to filter. When the client is found, click **Select**.
{% hint style="info" %}
If only tenant-level priorities are enabled, the user will go directly to Step 4.
{% endhint %}
Step 3: Click **Next**.
Step 4: Enter a priority name and additional information into the fields on the page.
1. **Priority (required**): The title of the priority.
2. **Status**: The status of the overall priority.
3. **Severity**: The severity of the overall priority.
4. **Priority author:** This value auto-populates with the user's email who created the priority. Another email can be selected by clicking within the box and choosing from the pulldown menu.
5. **Priority owner**: The priority owner. Select the priority owner(s) by clicking within the box and choosing from the pulldown menu.
6. **Identification date**: This is the date that the priority was identified. The priority may have been determined or observed at a prior date.
7. **Priority description**: An RTF field to enter the description of the priority.
8. **Recommendation**: 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.
9. **Treatment**: An RTF field to enter a treatment of the priority. Treatments are the remediation taken, often not the ideal recommendation due to resource and time constraints.
10. **Treatment owners**: A list of owner(s) who will own the priority treatment.
11. **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 (\_).
12. **Target remediation date**: 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.
13. **Actual remediation date**: Identifies the date that the priority was remediated. Place the cursor in the field box to select a date from the calendar.
14. **Likelihood (score)**: Select a number from one to ten to denote the probability that the findings and assets in this priority will result in malicious actions.
15. **Impact (score)**: Select a number from one to ten to denote the effects of malicious actions on the findings and assets in this priority.
16. **Priority score**: This value is the product of the two factors (likelihood and impact values) entered previously.
17. **Reason for score**: This field allows for an explanation for others on the rationale for entering the values used for the priority score.
Step 5: Scroll back to the top of the page and click **Save.**
The information entered is presented on the priority details page.
This page is the **Details** tab view, which is reached by clicking **View** under the "Actions" column in the row of an existing priority on the **Priorities** module home page.
---
# Agent Instructions: 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:
```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation/priorities/creating-a-priority.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.