> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/getting-started/set-up-your-isms/add-your-first-asset.md).
# Add your first asset
With your organisation's Harpe page, you can add assets that you own or tools that you use.
1. Open your organisation's Harpe page.
2. Click on the assets page on the left hand side of your screen.
3. You will see a page similar to this. Click on the `Add Asset` button to add an asset.
Assets page
4. There are three sections for each asset - `General Information` (as pictured below), `Assurance`, and `Disaster Recovery`. The `Disaster Recovery` field is hidden for all assets that are not marked as critical. For a comprehensive and compliant record, it is recommended to fill out all these fields. These can be filled out later if desired as asset compliance is tracked on the main Assets page.
New Asset form
5. Once all the required information is completed, click the `Add` button. You will then see your new asset in the list.
6. Add any further assets as necessary.
More comprehensive information can be found in the [Assets](/start/manual/assets.md) section of the wiki.
---
# 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://manual.harpe.io/start/getting-started/set-up-your-isms/add-your-first-asset.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.
