> 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/concepts/intermediate-concepts/it-asset.md).

# IT asset

Centralize IT inventory in Remote Desktop Manager by attaching hardware, software, and location details to entries for lifecycle tracking.

Manage your IT inventory accurately by centralizing technical, software, hardware, and location information. In Remote Desktop Manager, IT assets can be attached to a connection entry or managed with an asset manager, letting teams track lifecycle details such as owner, warranty, tags, and custom fields inside a vault. This centralization improves visibility, reduces duplication, and accelerates troubleshooting.

For scale, use templates and batch operations to import or update many assets at once, then keep records aligned through synchronizers or periodic updates. Reports and audits help validate accuracy and demonstrate compliance across environments.

#### Related topics

* [IT asset entry](/rdm/knowledge-base/how-to-articles/it-asset-entry.md)
* [Use the IT Asset Management feature in Remote Desktop Manager](/rdm/knowledge-base/how-to-articles/it-asset-management-in-remote-desktop-manager.md)
* [Hide the Asset panel located in the dashboard](/rdm/knowledge-base/how-to-articles/apply-policies-gpos.md#hide-the-asset-panel-located-in-the-dashboard)

#### See also

* [Devolutions Academy - Asset management](https://academy.devolutions.net/student/path/1925039/activity/2667189)


---

# 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/concepts/intermediate-concepts/it-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.