> 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/workspaces-and-drives/drive-settings.md). # Drive Settings Drive settings can be accessed by either right clicking on the drive in the left panel and selecting **Drive settings**, or by going to the workspace settings from the left panel and then scrolling down to the drive on the left. Drive settings can be controlled by anyone that has admin access on the workspace. This includes: * Changing the drive name * Changing the drive icon * Deleting the drive Note that **full access** drive members ***cannot*** change drive settings or metadata. Only workspace admins and drive managers can change settings and metadata. ## General * **General:** the drive icon and name * **Custom Mount Path:** override where the drive mounts on macOS, Linux, and Windows. Leave a path empty to use the system default. * **Storage:** **Maximum storage (GB)** sets the most storage this drive can use. Set it to 0 for unlimited storage. * **Bucket Info:** the cloud provider and region of the drive's bucket (plus the endpoint and bucket name for BYOS drives) * **Developers:** the Drive ID ## Other tabs * **Slack Notifications:** configure Slack delivery and notification preferences for this drive * **Permissions:** manage who has access to the drive * **Metadata:** manage metadata and add custom fields across the drive * **Shared links:** manage the drive's shared links * **Snapshots:** only available in the Shade desktop app --- # 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/workspaces-and-drives/drive-settings.md?ask=&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.