> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/getting-started/navigating-the-ui/data-manager.md).

# Data Manager: Upload Asset Data

Upload, tier, edit, and export your data.

### **Guided Demo**

To analyze an existing portfolio of assets, please upload your asset data via the Data Manager. Watch the guided demo below to get started.

{% embed url="<https://demo.alphageo.ai/demo/cmv99yff40x2vqmy8eyl2meld?utm_source=link>" %}

### **Important Note: Tiering your data (via the Data Upload Template)**

When uploading your properties, you are required to create your first tier. Tiering is essential for building parent/child hierarchies within your dataset. These hierarchies capture nuances like internal/ external reference data surrounding fund/ portfolio composition, including, but not limited to:

* Firm,
  * Fund,
    * Strategy
      * Manager/Operator,
        * Portfolio/Investment/Pool/Deal,
          * Capital Contribution,
            * Etc.\
              \
              ![](https://9348326.fs1.hubspotusercontent-na1.net/hubfs/9348326/Screenshot%202024-02-05%20at%2011-43-57%E2%80%AFAM-png.png)\
              ![](https://9348326.fs1.hubspotusercontent-na1.net/hubfs/9348326/Screenshot%202024-02-05%20at%2011-31-04%E2%80%AFAM-png.png)

*Tip: Swap "INSERT TIER 1 NAME (ex. Strategy)," etc., for your desired nomenclature - this will reflect in the UI & subsequent exports!*

Note: Each Tier 1, 2, and 3 has its own child tiers, and while the names could be the same, parent tiers are always unique.

Caution: Deleting a tier will remove the associated underlying data since the tier serves as a grouping mechanism. Alternatively, to retain the underlying data, update the current tier to another, and then proceed with the deletion of the now-empty, i.e., former parent tier.


---

# 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.alphageo.ai/getting-started/navigating-the-ui/data-manager.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.