> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/workspaces-faq/difference-between-a-workspace-and-a-drive.md).

# What's the difference between a workspace and a drive?

Workspace is the central location for you, your team, drives, and assets. This allows for easy permissions management across drives, unified billing across an organization, and logging for security and audit across files and assets. Workspaces can have as many drives of any type. Users can be added to a workspace with the following permissions:

Drives are the location in which you can house different sets of assets. You could choose to create a drive per project, per client, per shoot, or however you choose depending on you and your teams workflows.

Our recommended solution is to choose create a drive per client, and separate out folders for projects and shoots. This allows for maximum permission control and easy revocation and access expiration for external collaborators and workspace members.


---

# 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://academy.shade.inc/help-center/workspaces-faq/difference-between-a-workspace-and-a-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.
