> 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/pentest-management/how-it-works.md).
# How it Works
Catchify makes it easy to manage penetration testing from start to finish, all within one secure platform.
Here’s how a typical workflow looks:
* You create a new pentest request and select the target assets
* A Catchify engineer reviews the scope and provides a proposed plan
* You approve or request changes to the scope or timeline
* Once approved, the pentest is queued and scheduled
* On the scheduled start date, testing begins
* Your team receives real-time notifications for any discoveries
* You can log in any time to track progress, view reports, and add comments
* Findings are uploaded progressively to your dashboard
* You may request retesting through the platform once fixes are applied
* You can schedule recurring pentests based on your testing cycle
***
This streamlined process eliminates the need for back-and-forth emails and static reporting.\
Catchify ensures that findings are delivered as **actionable work items,** making remediation faster and more efficient.
---
# 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/pentest-management/how-it-works.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.