> 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/adding-assets.md). # Adding Assets Assets define what will be tested during your security engagement, such as websites, APIs, mobile apps, networks, and other critical systems. Assets represent the scope of your security testing and include websites, APIs, mobile apps, networks, and other systems. It's important to define these before engaging in any pentesting activity. ### 🛠️ How to Add an Asset 1. In the left-hand menu, click **Settings**

2. Select **Assets**

3. Click the **+ New Asset** button in the top-right

4. Fill out the **Asset Details**: * **Title** – Must be descriptive and unique

* **Description** – Example:\ `Primary website for Catchify, consisting of 20+ pages and multiple subdomains`

* **Domain** – `app.catchify.sa` * **IP Address** – Optional, for IP-based assets * **Asset Type** – Choose one: * Website * Web Application * Mobile Application * API * Network * Other * **Hosting Type** – Public Cloud, Private, etc. * **Environment** – (Production, Staging)

5. Click **Save** to register the asset.

--- # 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/adding-assets.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.