# Permission Inheritance Examples ### Scenario: Workspace Member + Drive Inheritance **You** * Role: **Workspace Member** * Not a workspace admin * You join a workspace that already has two drives *** ### Drive Setup (by an Admin) #### Drive A: `Marketing Project` * **Default inheritance for workspace members:** **Full Access** #### Drive B: `Finance & Legal` * **Default inheritance for workspace members:** **No Access** *** ### What You See When You Join the Workspace #### Drive A — `Marketing Project` Because the drive’s default inheritance is **Full Access**: * The drive appears in your drive list * You can open all folders and files * You can: * Upload files * Rename, delete, and reorganize files * Manage file- and folder-level permissions * You are **not** a Drive Manager * You cannot rename or delete the drive * You cannot manage drive-level permissions * You cannot manage metadata at the drive level *** #### Drive B — `Finance & Legal` Because the drive’s default inheritance is **No Access**: * The drive does **not** appear in your drive list * You cannot browse its folders or files * You have zero visibility that its contents even exist > In effect: > > **This drive is invisible to you unless someone explicitly adds you.** *** ### If an Admin Later Changes Something #### Case 1: Admin explicitly adds you to Drive B as an Editor * Drive B now appears in your drive list * You can access all folders and files in that drive * Your permissions are **Editor**, regardless of the default inheritance *** #### Case 2: Admin changes Drive B’s default inheritance to “Viewer” * You see the drive * You can view/download files, but not edit or upload ### Scenario: Workspace Contractor **You** * Role: **Workspace Contractor** * Same setup as before, two drives, one with “No Access”, and another with “Full Access” default inheritance *** ### What You See When You Join the Workspace #### Both Drives Are Invisible: Because contractors ignore default inheritance: * The drives do **not** appear in your drive list * You cannot browse their folders or files * You have zero visibility that their contents even exist *** ### If an Admin Later Changes Something #### Case 1: Admin explicitly adds you to Drive A as an Editor * Drive A now appears in your drive list * You can access all folders and files in that drive * Your permissions are **Editor**, regardless of the default inheritance *** #### Case 2: Admin adds you to a specific folder inside of Drive A * You see the drive * You can view and download files inside of that specific folder, and if you were to mount that drive you would only see that specific folder you were added to. * If you were added to a child folder, you would be able to navigate to that folder via the parent folder, but you **would not** be able to see any folders that you were not explicitly added to. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://academy.shade.inc/sharing-and-collaboration/permission-inheritance-examples.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.