> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/storage-and-transfer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/storage-and-transfer/managed-lab-storage/overview.md).
# Overview
**Managed Lab Storage** is a professionally managed storage service designed to provide researchers with an affordable, secure, and locally accessible storage solution for grant-funded research. The service is intended for workloads where enterprise-level performance and high resiliency are not the primary requirements, but where researchers benefit from low-latency access to data within or near their labs. Storage systems are purchased using research grant funds and deployed as consumer-grade NAS appliances, with OIT providing the initial configuration, ongoing operating system and firmware maintenance, and hardware replacement throughout the system’s lifecycle. This model provides researchers with greater control and convenient local access to their research data while reducing the cost and management burden associated with maintaining storage independently.
---
# 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.ccv.brown.edu/storage-and-transfer/managed-lab-storage/overview.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.
