# Assets Dashboard

The Assets Dashboard is a user-friendly feature that streamlines the asset management process, helping program managers to stay organised and on top of their bug bounty program.

<figure><img src="/files/8b7lTicTM95zkXDNFM4H" alt=""><figcaption></figcaption></figure>

### Adding an Asset

Adding an asset is easy, simply click the "Create Asset" button, fill in the necessary details such as the asset name, URL, asset type, and labels and click the "Save" button.   In case of websites, the URL is to be filled, and in case of mobile applications, the link to the respective app store is to be filled. Labels can be added to an asset, such as development, staging, or stack environment, to help hackers better understand the assets. This allows them to identify and report vulnerabilities more efficiently.

<figure><img src="/files/CVnpc0XBn3paP2XyGUZ3" alt=""><figcaption></figcaption></figure>

### Editing an Asset

Editing an asset is just as simple, by clicking pencil button next to existing asset name from the list, program manager can make necessary changes to the asset information. The program managers can also delete an asset by clicking on the cross button next to the asset name. This feature makes it easy for program managers to keep track of their assets, ensuring that all information is up-to-date and accurate, making it easier for hackers to identify and report vulnerabilities.

<figure><img src="/files/fviQRD0Z1hSboi7BvFZ5" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.bugbase.ai/company-guide/assets-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
