# Creating a Finding
Creating a finding within PlexTrac can be initiated either through the **Clients** module or the **Reports** module, but either approach involves selecting a report to add the findings. When created within PlexTrac, users can update using five tabs: **Finding** **Details**, **Affected** **Assets**, **Screenshots/Videos**, and **Code Samples**.
Step 1: From the **Reports** module, click the row of the impacted report.
Step 2: Click the **Findings** tab.
Step 3: Click **Create Finding** from the "Add Findings" pulldown menu.
Step 4: Enter a finding name and select the finding severity. Click **Create**.
Step 5: The edit finding page has four tabs for collecting data about a finding (further details on each tab are provided below).
1. **Title (required)**: All finding titles must be unique within a report. The tool will provide an error message after clicking Save if an existing title is used**.**
2. **Severity (required)**: Identifies the severity rating for the finding. The values are in ascending order: `Informational`, `Low`, `Medium`, `High`, and `Critical`.
3. **Score type:** Identifies the score associated with a finding. This can be used to record a general score, a CVSS 2.0 score, a CVSS 3.0 score, a CVSS 4.0 score, or [dynamically create a CVSS 3.1 score using the provided calculator](/plextrac-documentation/product-documentation/reports/findings/cvss-scoring.md).
4. **Priorities:** Associate the finding with a priority in the Priorities module.
5. **Status:** Defines the [status of the finding](https://docs.plextrac.com/plextrac-documentation/product-documentation/reports/add-custom-finding/draft-published-flag#finding-open-or-closed-status) (`Open`, `Closed`, or `In Process`). It defaults to `Open`.
6. **Sub-Status:** Provides further details on the status of a finding if [set up by admin](/plextrac-documentation/product-documentation-1/account-management/account-admin/tenant-settings/general-settings.md#manage-finding-sub-statuses). If no sub-status values have been configured, this field will not appear.
7. **Assigned to:** Identifies the user assigned to a finding. Only one user can be assigned, and an email will be sent once the finding is saved. The list in the pulldown menu is derived from the list of [users added to a client](/plextrac-documentation/product-documentation/clients/manage-client-users.md).
8. **Description (required):** An RTF field allowing content, images, links, code examples, tables, and lists to be entered as needed. This field has [collaborative editing](/plextrac-documentation/product-documentation/reports/findings/collaborative-editing.md) enabled.
9. **Recommendations:** An RTF field allowing content, images, links, code examples, tables, and lists to be entered as needed. This field has [collaborative editing](/plextrac-documentation/product-documentation/reports/findings/collaborative-editing.md) enabled.
10. **References:** An RTF field allowing content, images, links, code examples, tables, and lists to be entered as needed. It has [collaborative editing](/plextrac-documentation/product-documentation/reports/findings/collaborative-editing.md) enabled.
11. **CVE ID:** Common Vulnerabilities and Exposures (CVE) identifier(s) assigned to the finding. This field requires a format of *CVE prefix + Year + arbitrary digits*. There is no limit to the number of random digits.
* Example ID with four digits: `CVE-2014-3127`
* Example ID with five digits: `CVE-2018-54321`
* Example ID with six digits: `CVE-2019-456132`
12. **CWE ID:** The Common Weakness Enumeration (CWE) identifier(s) assigned to the finding. This field requires a two-to-four-digit number format.
* Example ID with two digits: `99`
* Example ID with three digits: `243`
* Example ID with four digits: `1423`
13. **Tags:** Stores any tags associated with a finding to help manage and retrieve the finding more easily later.
14. **Custom Fields**: Click **Add custom field** to insert more labels and values as needed.
Step 5: Click **Save**.
The information entered is now displayed in the **Findings Details** tab and can be modified as needed. More details of a finding can be added by continuing to the other available tabs.
## Affected Assets Tab
This tab displays any affected assets associated with a finding. The Affected Assets page provides more information on this topic, such as how to import or create.
## Screenshots/Videos Tab
This tab stores screenshots and videos associated with a finding, as videos are not allowed in the **Finding Details** rich-text fields.
To add a file, drag it onto the box on the page or click to navigate to files on the computer. Repeat as needed.
## Code Samples Tab
This tab stores any code samples related to a finding for future reference. Click **Add Section** to add additional sections. The code will be formatted when the report is published.
---
# 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/reports/findings/creating-a-finding.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.