> 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/what-are-workspaces.md).

# What are workspaces?

A workspace is where your team works in Shade. It holds your drives, which hold your files and folders, and it's where your internal team gets access to all of its media.

Put another way, a workspace is a collection of drives and a collection of people: the team you add once and then give access to the projects they work on.

### Workspace roles

People can be added to a workspace with one of these roles:

* **Owner:** the highest level of access. Owners can transfer ownership to an admin.
* **Admin:** full control over workspace settings, drives, and members. Admins can edit drive details, change storage locations, and more.
* **Member:** access to drives based on each drive's [inheritance](https://academy.shade.inc/help-center/drive-faq/what-is-drive-inheritance.md). Members can create drives for themselves and the team, and invite guests to specific drives or folders.
* **Contributor:** like a member, with inherited drive access, but can't create new drives.
* **Contractor:** doesn't inherit drive access. Contractors must be invited to specific drives, files, or folders.
* **Guest:** not part of the workspace. Guests only see the drives, files, or folders shared with them.

For what each role can do, see [Workspace and Drive Permissions](https://academy.shade.inc/sharing-and-collaboration/workspace-and-drive-permissions).

### Why have workspaces?

Workspaces bring everyone into one team with many drives connected to it. That gives you two things:

* **One team across projects:** add people once, then give them access to as many drives as they need.
* **Central management:** billing, permissions, and security logging are handled once for the whole workspace instead of per drive.

### What are you billed for?

Every Owner, Admin, Member, Contributor, and Contractor in your workspace is a billable seat. Guests aren't billed and don't use a seat, but each plan limits how many guests you can invite. Seat and guest limits are enforced when you invite people. See [How do seat limits work?](https://academy.shade.inc/help-center/billing/how-do-seat-limits-work.md) for each plan's limits.


---

# 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/what-are-workspaces.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.
