A Drive API integration must explicitly support shared drives and use the right search context. Adding supportsAllDrives does not grant membership or override permissions; it tells Drive that the application understands shared-drive behavior.
Set support for the relevant method
Google lists the v3 file, permission, and change methods that require shared-drive support. Use supportsAllDrives=true where documented and confirm that the authenticated identity is actually authorized for the target content.
Do not substitute a broad OAuth scope for missing shared-drive membership or an organization policy restriction.
Choose the intended listing corpus
For a specific shared drive, use the documented combination of corpora=drive, driveId for that drive, includeItemsFromAllDrives=true, and the supported-method flag. Retain the appropriate query and fields for the task.
Google recommends narrower user or drive corpora for efficiency when possible. An allDrives query can return incompleteSearch, so do not represent its first page or an incomplete response as an exhaustive organization-wide inventory.
Handle results and restrictions correctly
Follow nextPageToken through the required pages and check each returned file’s identity and capabilities. My Drive and shared drives have different ownership and permission models, so avoid assuming every item has the same individual-owner behavior. Change tracking also needs the correct shared-drive parameters and token context. Test with controlled accessible and inaccessible examples before relying on production coverage. Keep drive identifiers and relevant errors in protected diagnostics, and state which authorized corpus was actually searched rather than claiming the API found every file in the organization.
References
- Implement shared drive support | Google Drive | Google for Developers
- Search for files and folders | Google Drive | Google for Developers
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.