B
Brandon Upshaw
The Google Drive integration in Media Storage currently syncs only files owned by the connected Google account. Shared Drive content, files shared with the account, and shared-file shortcuts do not appear. The documented workaround is to copy files rather than shortcut them, which defeats the single source of truth that Shared Drives exist to provide.
Please extend the integration to cover:
  1. Google Shared Drives (Team Drives)
  2. Files shared with the connected account
  3. Google Drive shortcuts, resolved to their target file
Why this matters for agencies
Agencies are HighLevel's core customer, and agencies keep client assets in Shared Drives, because Shared Drive files survive staff turnover while My Drive files leave with the employee who owned them. Under the current owned-files-only behavior, the integration does not fit the way agencies actually store client media.
We manage church and clinic clients whose entire photo libraries, 100+ images each, live in Shared Drives. None of it is reachable through the integration today, so we still maintain a separate pipeline outside HighLevel just to get at those images.
Why this should be a small change
This looks like default query parameters on the Drive v3 files.list call rather than an architectural limit:
  • supportsAllDrives=true and includeItemsFromAllDrives=true
  • corpora=allDrives, or drives.list plus corpora=drive&driveId= to offer a Shared Drive picker
  • sharedWithMe=true for files shared with the connected account
  • resolve shortcutDetails.targetId for shortcut entries
Worth noting: the drive.readonly scope already required to browse a user's Drive also
covers Shared Drives that user can access, so existing connections would not need to re-authorize. This should be additive for every current user.
Related
"Connect Media files to a Google Drive Folder" (355 votes, shipped January 2025) has a comment asking for Shared Drive support. Filing separately because that request is closed and the comment is unlikely to be triaged.