> 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/getting-started.md).

# Getting Started

Whether you need storage for **research**, **departmental**, or **administrative** purposes, the recommended first step is to contact your department's IT support professionals (**ITSCs**). Your ITSC team can help you determine the appropriate storage configuration and coordinate the initial setup with the Storage team.

#### What can the ITSC team help with?

The ITSC team can assist with:

* **Determining your storage requirements:** Help identify an appropriate folder structure and access model based on your use case.
* **Creating and managing AD security groups:** Campus File Storage access is typically managed through Active Directory (AD) security groups. Your ITSC team can create the appropriate groups and manage group membership as users join or leave the project or department.

{% hint style="warning" %}
The storage team doesn't have access to create or manage AD security groups.
{% endhint %}

* **Planning folder permissions:** Advise on how to organize folders and configure permissions to ensure that users have appropriate access to the data they need.
* **Managing access:** Add or remove users from the appropriate AD security groups as access requirements change.
* **Submitting the storage request:** The ITSC team can submit the [**NAS Storage Request**](https://www.help.brown.edu/servicedesk/customer/portal/16/group/55) on your behalf and coordinate with the Storage team during the provisioning process.

#### Recommended onboarding process

1. **Contact your ITSC team** and describe your storage requirements, including the intended users, purpose of the storage, and approximate amount of data.
2. **Work with ITSC to define the folder structure and access requirements**, including which users or groups should have read or read/write access.
3. **ITSC creates the necessary AD security groups** and establishes the appropriate group membership.
4. **ITSC submits the NAS Storage Request** to the Storage team with the required configuration details.
5. **The Storage team provisions the storage** and works with ITSC to validate access and permissions.
6. **ITSC manages ongoing access** by maintaining the membership of the associated AD security groups.

Using your ITSC team as the initial point of contact helps ensure that the storage is configured with an appropriate access and permissions model from the beginning and provides a clear path for managing access throughout the life of the service.

If you are unsure which ITSC team supports your department or research group, refer to the [**ITSC team list**](https://sites.google.com/brown.edu/oit-handbook/supporting-our-services/itsc-list).

**Link to submit a** [**NAS Storage Request**](https://www.help.brown.edu/servicedesk/customer/portal/16/group/55)


---

# 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/getting-started.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.