> 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/virtual-folders-for-organising-drive-content.md).
# Virtual Folders For Organising Drive Content
space.vars.PRODUCT\_NAME supports a flexible method for arranging the contents of your network drives in the form of virtual folders. Virtual folders allow you to re-organise the structure of your SharePoint content without having to make any changes in SharePoint itself. Instead of connecting your network drive to a single target in SharePoint such as a site or a document library, create virtual folders within your network drive and connect each virtual folder to a different target in SharePoint.
For example; you may have a document library in one SharePoint site and a document library in a second SharePoint site, but you would like both libraries to show in a single network drive rather than a network drive for each document library. space.vars.PRODUCT\_NAME virtual folders permit you to connect the network drive to both document libraries.
The virtual folders can be nested too; permitting you to create a complex folder hierarchy in your network drive.
{% hint style="info" %}
See [Virtual Folders](/administration-guide/virtual-folders.md) on how to create a virtual folder in a network drive
{% endhint %}
---
# 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/virtual-folders-for-organising-drive-content.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.