> For the complete documentation index, see [llms.txt](https://ynteq.gitbook.io/ynteq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-assets.md).
# Managing Assets
This part of the Ynteq CMMS is the digital counterpart of your physical reality. A list of all assets, ordered with a custom grouping of your choosing.
## Asset overview
The Asset overview is build from different layers. First locations, followed by asset groups, then assets and finally sub-assets. You are able to manually create the correct hierarchy structure by sellecting layers and connecting them to the correct parent.
It is also possible to unfold the entire structure, or to use the specific filters to only see a specific location or asset group.
## Add an asset
Via the blue button in the top right corner it is possible to manually add an asset. The destined form will ask for a name, and there is the possibility to add a description and/or picture.
For the additional information it is important to select the asset's parent (to be placed correctly in the hierarchy). Furthermore it is possible to add extra information about the asset, and adding a maintenance strategy, criticallity and status.
---
# 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://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-assets.md?ask=&goal=
```
`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.