> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/solidred-documentation/3.1/entity-management-features/asset-management/add-asset.md).

# Add asset

This page explains the steps to take in order to add a new asset in SolidRed

In order to add an asset, click on the vertical ellipsis next to the existing asset under which you want the new asset to belong.

<figure><img src="https://content.gitbook.com/content/g2ULfgI3D3mQDYeAY5ti/blobs/rm5tgvPfgu63OO7HzU05/image.png" alt=""><figcaption><p>Add asset from the asset tree</p></figcaption></figure>

After clicking the **Add asset** option, the asset management screen will appear as shown below.

<figure><img src="https://content.gitbook.com/content/g2ULfgI3D3mQDYeAY5ti/blobs/emCLrMg8SJCaQVaUrOYo/image.png" alt=""><figcaption><p>Asset Management Screen</p></figcaption></figure>

Fill out the form with the requested information.

* **Asset name**: unique name of the asset. This field is required.
* **Description**: further details on the asset. This will be displayed below the name asset's name in the overview of the asset in question.&#x20;

After creating the asset, it will be part of the asset tree according to the parent asset selected.


---

# 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.twtg.io/docs/solidred-documentation/3.1/entity-management-features/asset-management/add-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.
