> For the complete documentation index, see [llms.txt](https://docs.zeedrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeedrive.com/feature-guide/map-to-all-modern-team-sites-under-a-single-drive.md).

# Map To All Modern Team Sites Under A Single Drive

<code class="expression">space.vars.PRODUCT\_NAME</code> can map a network drive to all the modern team sites that users have joined, including Microsoft Teams. Changes to user membership of modern team sites will automatically be reflected in the network drive; if users create a new modern team site, or join an existing one, then the new modern team site will appear in the user's mapped network drive in File Explorer automatically.

Create a new network drive and choose the 'Modern team sites' connection option.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FkonJ9uDkzAULaS5CVSsF%2Fimage.png?alt=media&amp;token=16c16978-3c27-4072-922b-1efdaeca45d4" alt=""><figcaption></figcaption></figure>

Click the Choose button to change how <code class="expression">space.vars.PRODUCT\_NAME</code> connects to the modern team sites. You can choose to connect only to the default document library in each site or to the entire site hierarchy.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FARnjW5X7L55ZYN0W5vUX%2Fimage.png?alt=media&amp;token=6f50e3fa-0bc8-4071-b936-4cf00abf7a6d" alt=""><figcaption></figcaption></figure>

Choose the default document library connection option if you employ only a single document library per modern team site or want your Microsoft Teams channels to appear directly below the modern team sites in File Explorer.

In this example two Microsoft Teams, Accounts and New Product, have a number of channels.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2F0ERibkAZ1uYk82mM2BLf%2Fimage.png?alt=media&amp;token=d2f2f2a1-0fdd-4dde-825a-a24f5d3a411a" alt=""><figcaption></figcaption></figure>

The channels will be shown directly below the Teams in File Explorer if the default document library option is selected.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2F5CLO5UkgHKYs0RfDEwmi%2Fimage.png?alt=media&amp;token=3088deab-ced2-4c82-b02a-9ae974ff6067" alt=""><figcaption></figcaption></figure>

For a step-by-step guide to configure a connection to Teams, see [Network Drive Connection Options](https://docs.zeedrive.com/administration-guide/network-drive-connection-options.md#modern-team-sites)


---

# 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.zeedrive.com/feature-guide/map-to-all-modern-team-sites-under-a-single-drive.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.
