> 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/manual/assets/viewing-an-asset.md).
# Viewing an Asset
Clicking on an asset will take you to a more detailed view of the asset. Here there are three sections - Overview, Assurance, and Disaster Recovery.
{% tabs %}
{% tab title="Overview" %}
The `Overview` tab shows a basic look at the selected asset. From here you can view the description of the asset, leave comments, upload files, and view any activity on the asset.
The main sections can be edited by clicking the `Edit` button in the top-right, and side-bar information can be edited with the bottom-left `Edit` button.
Asset overview
{% endtab %}
{% tab title="Assurance" %}
The `Assurance` tab is key to ensuring your asset is secured and correctly configured. Here you should log the basic security considerations to ensure your asset remains as secure as possible.
The main sections can be edited by clicking the `Edit` button in the top-right, and side-bar information can be edited with the bottom-left `Edit` button.
Asset assurance
{% endtab %}
{% tab title="Disaster Recovery" %}
The `Disaster Recovery` tab is important to ensure your assets have contingencies in place in case of an emergency. Each asset should have a disaster recovery plan prepared with notes regarding security considerations below. Effective disaster recovery measures can help your employees streamline and save processes in case of disaster.
The main sections can be edited by clicking the `Edit` button in the top-right, and side-bar information can be edited with the bottom-left `Edit` button.
Asset disaster recovery
{% endtab %}
{% endtabs %}
---
# 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/manual/assets/viewing-an-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.
