> 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/knowledge-base/how-to-articles/it-asset-entry.md).

# IT asset entry

Create an IT Asset entry in Remote Desktop Manager to track computers, monitors, printers, and their owner assignment history over time.

The ***IT Asset*** entry is useful for storing information about a large number of IT assets, such as computers, monitors, printers, and their status.

### Create an IT asset entry

1. In Remote Desktop Manager, create a new entry.
2. Select ***IT Asset Management***.
3. Choose the type of ***IT Asset*** you want to list.
4. Click ***Select*** to create the entry.
5. Enter the information and click ***Add***.

The entry is saved.

### Owner History

You can view the history of people previously assigned to an asset, along with start and end dates.

1. Select ***Owner History***.
2. The ***Owner History*** window opens.
3. A new ***Owner History item*** can be added by clicking ***Add (+)***.
4. Enter the ***End date***, ***Contact***, and ***Note***.
5. Click ***OK***.
6. Click ***Save*** to save the Owner history.

#### See also

* [Devolutions Academy - Asset Management](https://academy.devolutions.net/student/path/1925039/activity/2667189)
* [Devolutions Academy – Must-know features to boost productivity](https://academy.devolutions.net/student/page/3266674-must-know-features-to-boost-productivity?sid=66acc46b-f563-44e0-a318-00bfeaa0a374\&sid_i=0)


---

# 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/knowledge-base/how-to-articles/it-asset-entry.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.