> 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/workspace-settings.md). # Workspace Settings Workspace members and admins have access to different workspace settings from the workspace settings page. ## Workspace Members and Guests Everyone can leave a workspace from the **General** tab. Workspace members can also open **For Developers** under Integrate, which shows the Workspace ID, the **Webhooks Dashboard**, and the **Zapier Integration Key**. Everyone can manage their own **API keys**, **S3 API keys**, and **MCP Connections** under Integrate. ## Workspace Admins Admins can change anyone’s permission in the workspace and see these tabs under My Workspace: * **General:** change the workspace logo and name, connect the Slack integration, manage workspace folder templates with **Manage Templates**, and delete the workspace * **Members:** invite new members and manage everyone in the workspace across the Members, Contractors, Guests, and Groups tabs. This is also where admins set **Default Access for New Drives**, the access level workspace members inherit when new drives are created. It only affects new drives; after changing it, you can choose whether to update any existing drives to match. * **Sharing:** turn link sharing on or off, allow or restrict custom links, and default new comments to internal * **Usage:** monitor storage, seats, and guests, and free up storage with the File Manager * **Enterprise** (Enterprise plan only): manage SSO, Directory Sync (SCIM), audit logs, and domain verification ## Workspace Owner The owner has all admin settings plus the **Billing** tab, where they can manage the plan, seats, storage, and invoices. See [Billing](/administration-and-security/billing.md). Cannot leave a workspace without assigning ownership to someone else first. Ownership can only be assigned to workspace admins. --- # 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/workspace-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.