> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/user-interface/content-area/dashboard/dashboard-tabs/asset.md).

# Asset

Discover the Asset dashboard tab in Remote Desktop Manager, covering Summary, Software, Hardware, Contact, and Purchase information sections.

The ***Asset*** dashboard tab contains a wide assortment of information about the selected entry—some purely informative and some of operational nature. The tab contains multiple sections to present as much information as possible.

<table><thead><tr><th width="134">SECTIONS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Summary</strong></td><td>Allows uers to specify the computer specific information such as operating system, MAC address, and the hardware description.</td></tr><tr><td><strong>Software</strong></td><td>Allows users to list all software installed on the remote computer.</td></tr><tr><td><strong>Hardware</strong></td><td>Allows users to specify the hardware information of the remote computer.</td></tr><tr><td><strong>Contact</strong></td><td>Displays information on a person that has a link to the entry. It could be the technician managing the remote machine, for example.</td></tr><tr><td><strong>Purchase</strong></td><td>Allows users to enter information related to the invoice or the purchase of the equipment.</td></tr></tbody></table>


---

# 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.devolutions.net/rdm/user-interface/content-area/dashboard/dashboard-tabs/asset.md?ask=<question>&goal=<user_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.