> For the complete documentation index, see [llms.txt](https://help.quickappflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quickappflow.com/asset-management/asset-type.md).

# Asset Type

Click on three vertical line (hamburger) and Go to **Asset.**

![](/files/1Sp8hjUSDJvvRSZ27TL7)

User can add asset type when click on type menu.

![](/files/0URkAHTJp4xRA244pdUl)

Click on **+Type** for adding asset type.

![](/files/X9GzCq6niqET8a7t2gwF)

Add asset type name and description and click on Save.

![](/files/JTtlFqPMDfonSBVpxzlo)

Latest created type show on the top.

![](/files/mKAU1GfOGoaKMlrvWxG2)

The user can edit, delete, and view the asset type.

Click on the three-dot action menu.

To view asset type details, click on "**View**."

To edit asset type details, click on "**Edit**," make the changes you want, and then click on "Save."

To delete the asset type, click on "**Delete**." After clicking, a confirmation message will be shown. Click on "Confirm."

![](/files/SDaOXL2q75Hek441TAEt)


---

# 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://help.quickappflow.com/asset-management/asset-type.md?ask=<question>&goal=<endgoal>
```

`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.