> 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/drive-faq/shen-me-shi-qu-dong-qi-ji-cheng.md).

# 什么是驱动器继承？

驱动器继承是驱动器授予工作区成员的默认权限。每位未被以其他权限明确添加到该驱动器的工作区成员都会获得此默认权限。例如，如果新驱动器的继承权限为 **完全访问权限**，则每位工作区成员都拥有该驱动器的完全访问权限。

驱动器的任何管理员或工作区管理员都可以更改驱动器的继承权限。请前往 **设置 > 驱动器 > \<drive name> > 成员 > 默认继承权限**.

![更改驱动器的默认继承权限](https://2008292298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlvHrZ4ybpa07fNCxAfwz%2Fuploads%2FdSosTE6UzTa8HPZTBMQW%2Fdrive-default-inheritance.png?alt=media)

更多示例请参见 [权限继承示例](https://academy.shade.inc/sharing-and-collaboration/permission-inheritance-examples).


---

# 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/drive-faq/shen-me-shi-qu-dong-qi-ji-cheng.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.
