> 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
Understand the full pentest lifecycle in Catchify, from request to kickoff, findings, and retesting, all managed in one streamlined workflow.
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
