> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/asset-management/settings/asset-models.md).
# Asset Models
## 1 - Creating a Single Asset Model Upload
1. Click the "+ button" and select "Create".
2. Fill in all the applicable fields for your asset model. The more information you input, the better search data you will have.
3. Select Create and your Asset Model will immediately appear in the table.
## 2 - Bulk Create in the System
1. Click the "+ button" and select "Bulk Create".
2. Insert your asset data into the fields. Either tab through to get new rows, or click "+ Add Row" to get new rows.
3. Click Save.
4. You will receive an email when the bulk upload is completed.
## 3 - Bulk Create through Upload
If you have your own CSV, you will not need to do steps 1-2.
1. Download our template by clicking the "+ button" and selecting "Download Template".
2. Fill in the template for your asset models you would like to upload
3. Upload your template into our system.
4. Map your headers. Make sure that all headers are either green or yellow. **\*Any red headers will not allow you to move on to the next screen.**
5. Map your data. You can edit any data on this screen if needed by clicking the "+" signs off to the side, under Action.
6. Click Next.
7. Confirm your upload.
8. You will receive an email when the upload is complete.
---
# 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.adminremix.com/asset-management/settings/asset-models.md?ask=&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.
