> 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/getting-started/publish-your-docs.md). # Understand the Structure {% embed url="" %} ## **Why did you design Shade this way?** When we started Shade, we wanted to build a system that was intuitive to the experiences that we are all used to (like Google Drive or Dropbox), but also had the capabilities of modern productivity software like Notion and Figma. The Shade structure is defined to allow for a large amount of flexibility in how you’d like to structure your teams projects and work. You also have the ability to easily manage inheritance levels between members and guests. Shade is designed to be a file system solution that not only offers superior search capabilities, but also a premium experience when it comes to managing external collaborators, team members, and assets. ## What is a workspace? Workspaces are the base of Shade and is the top level in which you unify you, your team, projects, and assets. Simply, a workspace is a collection of drives and users. This is the “team” where you add members that will be involved in multiple projects. Your team is billed at the workspace level, which is the number of seats plus the amount of storage your workspace has purchased. See how billing works at [Billing](/administration-and-security/billing.md). ### Creating a new workspace: After you sign up for an account, you'll name and create your first workspace, along with your first drive, during onboarding. You can switch between any number of workspaces from the workspace dropdown in the top left of the app. Each workspace is billed separately. ### Deleting a workspace: Workspace admins can delete a workspace from Settings/General - this action cannot be undone. ### Renaming a workspace: Workspace admins can rename a workspace from Settings/General. ### Workspace permissions: **Workspace Members:** Your core team that can: * Manage drive configurations * Create and delete drives * Manage drive access for guests * Manage file and folder permissions for guests **Workspace Contributors** - Can edit items in the drives they inherit access to, but cannot create drives. **Workspace Contractors** - Members that don't inherit access from the workspace. Contractors have to be added manually to each drive, folder, or file. **Workspace Admins** - Member level permissions and: * Add workspace members * View workspace usage details **Workspace Owner** - Admin level permissions and: * Manage billing * Transfer ownership of the workspace {% content-ref url="/pages/8C73p2MA9ly4XcKKZpck" %} [Workspace and Drive Permissions](/sharing-and-collaboration/workspace-and-drive-permissions.md) {% endcontent-ref %} ## What are drives? We created one more level to organize your media between the workspace level and your folders. When you use the desktop app, the drive is the level that can be mounted to your computer like a hard drive. You can create a drive per project, per client, per shoot, or however you choose depending on you and your teams workflows. Our recommended solution is to choose a drive per client with separate folders for projects and shoots. This allows for maximum permission control, easy revocation, and access expiration for external collaborators and workspace members. See more organization tips at [Designing Your Permission Hierarchy](/sharing-and-collaboration/designing-your-permission-hierarchy.md#drive-level-access). ### Deleting a Drive: Drive admins can delete a drive from Settings/\[drive name]/General. This action cannot be undone. ### Renaming a Drive: Drive admins can rename a drive from Settings/\[drive name]/General. Note that mounted drives will not have their name changed until you re-mount the drive. --- # 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/getting-started/publish-your-docs.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.