> 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/campus-file-storage/how-to-connect.md). # How to Connect Campus File Storage (Files22) is accessible directly from the Brown University campus network or from off-campus locations via a secure VPN. The system supports native integration with Windows, macOS, and Linux; specific configuration steps for each operating system are detailed below. Additionally, files22 can be accessed through the university’s Remote App servers. For users operating within the OSCAR high-performance computing environment, access is restricted to research shares only. Please refer to the Center for Computation and Visualization (CCV) documentation for specific instructions on connecting to these research shares from within the OSCAR environment. --- # 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/campus-file-storage/how-to-connect.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.