[null,null,["上次更新時間:2025-08-04 (世界標準時間)。"],[],[],null,["# Shared drives overview\n\nA shared drive is an organizational structure within Google Drive that lives\nparallel to [My Drive](/workspace/drive/api/guides/about-files#my-drive).\nShared drives support files owned by an organization rather than an individual\nuser. An individual file can be organized within a shared drive or My\nDrive, but not both. However, [Drive\nshortcuts](/workspace/drive/api/guides/shortcuts) can be used to point to files or folders\nfrom shared drives to My Drive, or the other way around.\n\nAccess control\n--------------\n\nShared drives use a permission model similar to other content in\nDrive. Unlike files in My Drive, a group of users\nowns content within a shared drive. For more information about permissions, see\n[Share files, folders, and drives](/workspace/drive/api/guides/manage-sharing).\n\n### Permission propagation\n\nLike items in My Drive, permissions on parent items propagate\ndownward to their children. However, within a shared drive, permissions are\nstrictly expansive. For example, a user that has `role=commenter` for a shared\ndrive cannot have their access level reduced at another point within the folder\nhierarchy. However, their access can be increased for a certain set of files.\n\nShared drive files must have exactly one parent. This means that shared drive\nfiles belong to a single shared drive and are located in a single location\nwithin that shared drive. Having a single location simplifies permission rules\nfor shared drive files.\n\n### Compare member and file access\n\nThere are two classes of [`permissions`](/workspace/drive/api/reference/rest/v3/permissions) in\nshared drives:\n\n- *Member permissions* are for users who have been granted access to the\n shared drive, either directly or through a group. Members can view the\n shared drive metadata, such as the shared drive's name. Members have access\n to all files within the shared drive, with the access level depending on the\n `role` given to the member, such as `commenter` or `reader`.\n\n- *File access permissions* are for users who have been granted access to a\n subset of files within the shared drive. For example, sharing a single file\n to a user creates a file access permission.\n\nAn individual user can be a member of a shared drive *and* have file access\npermissions for files contained within the shared drive. A file access\npermission might be superseded if the user's membership in the shared drive\ngrants them a greater level of access.\n\nFile permissions are revoked when the user is no longer a member of the shared\ndrive, or if their member access level is reduced. Users also lose access to any\nfiles and folders in the shared drive that were directly shared with them.\n\n### Roles for shared drives\n\nAs with items in My Drive, each user in a shared drive is granted\naccess with a specific role. These roles are used for shared drives:\n\n- The `fileOrganizer` role allows users to organize files within a shared\n drive and to move content into the trash.\n\n- The `organizer` role grants the same privileges as the `fileOrganizer`. It\n also allows users to permanently remove content and modify shared drive name\n and membership.\n\n- The `writer` role allows users to add files to shared drives and to share a\n shared drive item.\n\nThe `owner` role isn't allowed in shared drives.\n\nFor more information about roles and operations allowed in a shared drive, see\n[Roles and permissions](/workspace/drive/api/guides/ref-roles).\n\n### Members and organizer rules\n\nShared drives have both the `organizerCount` and `memberCount` fields. The\nvalues for these fields can decide who can access the shared drive. The\nfollowing are the rules for `organizerCount` and `memberCount` fields:\n\n- Only administrators can manage a shared drive with an `organizerCount` of\n zero.\n\n- Only administrators can access a shared drive with a `memberCount` of zero.\n\n- Only administrators can access a shared drive with an `organizerCount` or\n `memberCount` greater than zero. This applies only if the remaining\n permissions are for empty groups or external users that were added before\n turning off sharing outside the domain.\n\n- The `organizerCount` and `memberCount` fields don't distinguish between\n members of the organization and external members.\n\n- Entities written on the file permission can access files inside a shared\n drive with a `memberCount` of zero.\n\n| **Note:** Service accounts don't have storage quota and can't own any files. Instead, they must upload files and folders into shared drives, or use OAuth 2.0 to upload items on behalf of a human user.\n\nFor more information, see [Search for shared\ndrives](/workspace/drive/api/guides/search-shareddrives).\n\nRelated topics\n--------------\n\n- [Manage folders with limited and expansive access](/workspace/drive/api/guides/limited-expansive-access)\n- [Create a shortcut to a Drive file](/workspace/drive/api/guides/shortcuts)\n- [How file access works in shared drives](https://support.google.com/a/users/answer/12380484)"]]