> 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/shade-academy/shade-academy-zh/gong-zuo-qu-he-qu-dong-qi/drive-settings.md).

# 驱动器设置

可以通过在左侧面板中右键单击该驱动器并选择 **驱动器设置**，或者从左侧面板进入工作区设置，然后向下滚动到左侧的该驱动器。

任何拥有该工作区管理员权限的人都可以管理驱动器设置。这包括：

* 更改驱动器名称
* 更改驱动器图标
* 删除驱动器

请注意 **完全访问权限** 驱动器成员 ***无法*** 更改驱动器设置或元数据。只有工作区管理员和驱动器管理者可以更改设置和元数据。

## 常规

* **常规：** 驱动器图标和名称
* **自定义挂载路径：** 覆盖驱动器在 macOS、Linux 和 Windows 上的挂载位置。将路径留空可使用系统默认值。
* **存储：** **最大存储空间（GB）** 设置此驱动器可使用的最大存储空间。将其设为 0 表示无限存储。
* **存储桶信息：** 驱动器存储桶的云服务提供商和区域（对于 BYOS 驱动器，还包括终端节点和存储桶名称）
* **开发者：** 驱动器 ID

## 其他标签页

* **Slack 通知：** 为此驱动器配置 Slack 发送和通知偏好
* **权限：** 管理谁可以访问该驱动器
* **元数据：** 管理元数据并在整个驱动器中添加自定义字段
* **共享链接：** 管理该驱动器的共享链接
* **快照：** 仅在 Shade 桌面应用中可用


---

# 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/shade-academy/shade-academy-zh/gong-zuo-qu-he-qu-dong-qi/drive-settings.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.