> 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/quickstart/the-contacts.md).
# The Contacts
Contacts in Catchify are stakeholders and key individuals who should receive notifications about project updates, security findings, and audit reports.
To add someone as a contact, they must first be added as a **user** in the system.\
➡️ [Click here to learn how to add users](/portal-guide/quickstart/adding-users.md)
### 🛠️ How to Set Up Contacts
1. Go to **Settings** in the left-hand menu
2. Click on **Company Info**
3. Click the **Edit** button from the top-right section of the form
4. In the contact fields, assign the appropriate users to each role:
* **Main** – Typically the administrator and project owner
* **Compliance** – Your compliance officer
* **Technical** – A lead developer or technical owner
* **Finance** – The person handling budgeting or approvals
These contacts will automatically receive updates:
* When project status changes
* During key phases of the pentest
* Upon completion and during approval workflows
---
# 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/quickstart/the-contacts.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.
