> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/mymove-manual/repository.md).

# Repository

The **Repository** page is a tool designed to manage and view files uploaded by all users within the platform. Supporting a wide range of file formats, including images, PDFs, CSVs, and more, the Repository allows uploads up to 500MB. This tool enhances team collaboration for structural monitoring projects by serving as a central hub where members can store and share key documents.

Users can upload data analyses, reports, studies, sets of photographs, and other important resources, ensuring that everyone on the team has access to the latest information. By consolidating all project files in one place, the Repository streamlines communication and decision-making, allowing for a more efficient and coordinated approach to the monitoring process.

<figure><img src="https://2601070869-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGk0mQOwBMc98gG9hlKRS%2Fuploads%2Fj5aW2DdQEuFC4nMIkjyk%2FRepository.png?alt=media&amp;token=a2d51614-57b8-49c6-8ca0-88c8ab1bc0c0" alt=""><figcaption></figcaption></figure>


---

# 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://move-solutions.gitbook.io/untitled/mymove-manual/repository.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.