> For the complete documentation index, see [llms.txt](https://docs.catchify.sa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catchify.sa/portal-guide/findings-management/findings-status.md).
# Findings Status
Finding status helps your team manage remediation and coordinate retesting with Catchify’s pentesters. As your developers take action on each finding, you can update its status to reflect progress.
### 🔄 Status Options
* **Pending Fix** – Finding is newly reported and awaiting developer action
* **Fixed** – The issue has been remediated and no retest is needed
* **Ready Retest** – The issue is fixed and you're requesting validation
* **Accepted** – The risk is acknowledged and accepted as-is by your team
***
### ✅ To Update a Finding Status
1. Click **Pentests** from the left-hand menu
2. Select the pentest you want to manage
3. Click the **Findings** tab
4. Click the specific **Finding** you want to update
5. Scroll down and choose a new status from the dropdown
6. Click **Submit** to save
***
This process ensures your remediation flow is visible and organized for both your team and the pentester.
---
# 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.catchify.sa/portal-guide/findings-management/findings-status.md?ask=&goal=
```
`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.