> 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-drives-by-group-membership.md).

# Map Drives By Group Membership

Network drives can be targeted to members of specific groups, similar to a Windows Group Policy Object. For example, through groups you can limit a network drive to map only for users in a given department, or geographic region; create an "Accounting" or "HR" group, or a "New York" or "London" group - add members to the group and associate that with the network drive. The network drive will be mapped only for the members of the group.

The configuration of the drives and your group targeting settings are stored centrally in the <code class="expression">space.vars.PRODUCT\_NAME</code> service meaning there is no dependency on Windows Group Policy and your settings will apply on any computer <code class="expression">space.vars.PRODUCT\_NAME</code> is activated whether the computer is joined to a domain or not.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FOOueuHMXV3lPkqqsPI8C%2Fimage.png?alt=media&amp;token=c7c4ff33-8fb5-4948-ab3e-6c3a9312f0f5" alt=""><figcaption><p>The group targeting configuration screen</p></figcaption></figure>

For a step-by-step guide on configuring group targeting, see [Group Targeting](https://docs.zeedrive.com/administration-guide/group-targeting.md).


---

# 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-drives-by-group-membership.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.
