> 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/help-center-zh/workspaces-faq/shen-me-shi-gong-zuo-qu.md).

# 什么是工作区？

工作区是您的团队在 Shade 中开展工作的地方。它包含您的驱动器，驱动器中存放文件和文件夹；您的内部团队也在这里访问全部媒体。

换句话说，工作区是驱动器和人员的集合：您一次添加团队成员，然后向他们授予其所参与项目的访问权限。

### 工作区角色

可以将人员以以下任一角色添加到工作区：

* **所有者：** 最高级别的访问权限。所有者可将所有权转移给管理员。
* **管理员：** 可完全控制工作区设置、驱动器和成员。管理员可以编辑驱动器详情、更改存储位置等。
* **成员：** 可根据每个驱动器的 [继承权限](/help-center/help-center-zh/drive-faq/shen-me-shi-qu-dong-qi-ji-cheng.md)。成员可以为自己和团队创建驱动器，并邀请访客访问特定驱动器或文件夹。
* **贡献者：** 与成员类似，可继承驱动器访问权限，但不能创建新的驱动器。
* **承包商：** 不继承驱动器访问权限。承包商必须被邀请到特定的驱动器、文件或文件夹。
* **访客：** 不属于工作区。访客只能看到与其共享的驱动器、文件或文件夹。

关于各角色可执行的操作，请参阅 [工作区和驱动器权限](https://academy.shade.inc/sharing-and-collaboration/workspace-and-drive-permissions).

### 为什么要使用工作区？

工作区将所有人汇聚到同一个团队，并将多个驱动器连接到该团队。这为您带来两点好处：

* **跨项目的同一团队：** 只需添加一次人员，然后根据需要向他们授予多个驱动器的访问权限。
* **集中管理：** 账单、权限和安全日志均可在整个工作区层面统一处理，而不是按驱动器分别处理。

### 计费项目有哪些？

您工作区中的每位所有者、管理员、成员、贡献者和承包商都占用一个可计费席位。访客不计费，也不占用席位，但每个方案都会限制您可邀请的访客数量。邀请人员时会强制执行席位和访客上限。请参阅 [席位上限如何运作？](/help-center/help-center-zh/ji-fei/xi-wei-xian-zhi-ru-he-yun-zuo.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://academy.shade.inc/help-center/help-center-zh/workspaces-faq/shen-me-shi-gong-zuo-qu.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.