> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/assets/create-asset.md).
# Create Asset
Log in to your Aranet Cloud workspace as Administrator and navigate to the **ASSETS** menu.\
Switch to the **ASSETS** tab and click on the **NEW ASSET** button:
Give Asset a name and description and click on the **CREATE** button:
A pop-up window will open. On the left, there is a list of all sensors (physical and virtual) available in your Workspace. On the right, there is a timeline with the current date and time marked.
Sensors available for attaching to the Asset are marked with a green flag icon. 
Sensors already attached to the Assets are marked with a yellow flag icon. 
To attach the sensor to the asset, drag and drop it to the timeline:
Now you can edit a measurement point by clicking on the pencil icon. 
You can change its name and select the metrics needed. When all is done, click the **SAVE** button:
If you click on the sensors ribbon on the timeline, the pencil icon will appear. This allows you to edit the sensors linked to the timeline:
You can set the sensor Placement and Removal (if needed) date and time. By default, the sensor is placed without a Removal time. Pressing on **FILL AVAILABLE TIME** button will extend the sensors link from the date of the earliest sensors measurement time available in Cloud as Placement, and till the next sensors placement time to the same measurement point (if this was planned and placed before).
When you finish with sensor link editing, click the **SAVE** button, and you can continue with other sensors, adding to the asset. Adding other sensors, you don't need to save anything; all changes are saved automatically and immediately after they are made.
---
# 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.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/assets/create-asset.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.