Google Drive

With the Masset for Google Drive integration, you can bring your Google Drive files into Masset as assets without downloading and re-uploading them by hand. It connects your Google Drive files to Masset assets for import, preview, and syncing, so the content you already keep in Drive can live alongside the rest of your approved content in Masset.

The integration is import-oriented: files flow from Google Drive into Masset. Nothing is written back to your Drive. Access is granted on a per-file basis using Google’s file picker, so Masset only ever sees the specific files you choose to connect.

Using the Masset for Google Drive integration, you can:

1. Import Google Drive files directly as Masset assets, including files from shared drives.
2. Link private Google Drive files to Masset assets and grant Masset access to just those files.
3. Generate previews of private Google Drive files so they are viewable inside Masset.
4. Auto-extract metadata such as the file name and description from a Google Drive link.
5. Sync updates made to a Google Drive file back into the associated Masset asset.

Supported files

Masset can import both regular files and native Google Workspace files:

1. Standard files (PDFs, images, videos, Office documents, and other binary files) are imported directly.
2. Google Workspace files are exported to a portable format on import — Google Docs become PDF, Google Slides become PowerPoint (.pptx), and Google Sheets become Excel (.xlsx).
3. Shared drive files are supported in addition to files in a user’s My Drive.

Masset can read metadata and generate previews for public Google Drive links without a connected account. Working with private files — importing them, previewing them, or syncing updates — requires a connected Google account that has granted Masset access to those specific files.

Google Drive features

The Google Drive integration uses Google’s file picker to grant access one file at a time. When you connect a file, Masset gains access only to that file — not your entire Drive. The files you have shared with Masset appear as Permitted Files on the connected account, so you can always see exactly what Masset can reach and revoke access at any time from Google.

Because Google Drive files are often sensitive, private files are always accessed as the user who connected them. Each user connects their own Google account and shares their own files, and Masset honors that per-user, per-file access when importing content, generating previews, and extracting metadata.

Installation

The Google Drive integration is enabled at the company level and then connected per user. A Masset Admin enables the integration once, and each user who wants to import from Drive connects their own Google account.

To connect a Google account:

Once connected, you can import Google Drive files whenever you upload assets. On the asset upload screen, choose Import using integrations, then either pick files from a connected account or use the Connect Google Drive Account card to add a new one. Selecting files opens the Google picker, where you can choose files — including from folders and shared drives — to import or link into Masset.

Troubleshooting

Connected accounts are missing the “drive.file” permission

Symptom: A user has connected their Google account, but Masset still can’t import, preview, or sync their private Google Drive files. This usually means the connected account is missing the https://www.googleapis.com/auth/drive.file permission (scope) that Masset needs to access the files a user selects.

Cause: This most often happens when the user’s organization uses Google Workspace and their admin restricts which third-party apps may access Workspace data. When Masset isn’t trusted for the requested access, Google can decline to grant the drive.file permission during sign-in — so the account connects, but without the access Masset needs.

Fix (Google Workspace admin): A Google Workspace administrator needs to allow Masset to receive the drive.file permission from the Google Admin console:

1. Go to Security → Access and data control → API controls → App access control and open Manage App Access.
2. Find the Masset app. If a user has already tried to connect their account from Masset, the app appears automatically in your list of configured apps — search for it by name (Masset). Masset is not distributed through the Google Workspace Marketplace; it appears because a user in your domain went through the Google sign-in consent flow. To whitelist Masset before anyone has connected, use Add app → OAuth App Name or Client ID and contact support@getmasset.com for the exact OAuth Client ID.
3. Choose how much access to grant:
   • Quick fix: set the Masset app’s access to Trusted. Trusted apps are allowed to receive the scopes they request.
   • Least-privilege alternative (for security-strict organizations): set the access level to Specific Google data and allow the scopes the integration requests. Masset needs all of its requested scopes to be approved for a connection to succeed — https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/userinfo.email, and openid (see the scopes table below) — so allowing drive.file alone is not enough; the sign-in scopes must be approved as well.
4. Have each affected user disconnect and reconnect their Google account in Masset (Admin → Integrations) so Google re-issues access that includes the drive.file permission.

A connected Google account keeps needing to be reconnected

Symptom: A Google account that was working before now shows as disconnected or fails when Masset tries to access its files, and the user is prompted to reconnect.

Cause: Google issues Masset a refresh token when a user connects their account, and Masset uses it to keep the connection alive. Google can expire or revoke that token for several reasons, all of which require the user to reconnect. Per Google’s refresh token expiration guidance, the most common causes are:

1. Access was revoked. The user (or their Google admin) removed Masset from their Google Account’s connected apps.
2. The connection went unused for six months. Google expires a refresh token that hasn’t been used to obtain access for six months.
3. Too many active connections. Google limits how many active tokens a user can have for a given app; when that limit is exceeded, older connections stop working.
4. A Google account security event. Google can invalidate tokens at any time through its automated or manual security processes following account or security changes.
5. The app’s access was restricted. If a Workspace admin restricts a requested service, or the app is no longer approved for its scopes, Google can revoke the connection. This is the same admin control described in the missing drive.file permission section above.

Fix: Reconnect the affected account in Masset from Admin → Integrations (or use the Connect Google Drive Account card during upload). Reconnecting re-establishes access, and no previously imported assets are lost.

FAQ

What permissions (scopes) does the integration require?

To provide the described functionality, the Masset for Google Drive integration requests the following permissions from Google.

What Google Drive data does Masset have access to?

Masset only accesses the specific files a user shares with it through the Google picker. It cannot browse, search, or read a user’s full Google Drive.

For the files a user selects, Masset accesses:

1. The file contents, in order to import the file, generate a preview, and sync updates.
2. Basic file metadata such as the name and description, used to populate the corresponding Masset asset.

The files a user has shared are always visible as Permitted Files on their connected account, and access can be revoked at any time from Google.

What Masset data is shared with Google?

Nothing beyond what is required to sign in and read the selected files. The integration reads content and metadata from Google Drive into Masset; it does not upload Masset assets, analytics, or other Masset data into Google Drive.

Does the Google Drive integration use any sub-processors?

The Google Drive Integration does not currently use or require any additional sub-processors beyond the default set used by the Masset platform. We understand and respect the concerns that companies have about allowing third-party sub-processors access to your data.

If Masset introduces functionality requiring additional sub-processors, these features will be explicitly opt-in for all Masset customers to ensure that data is protected.

Does the Google Drive integration use my data for AI training?

No. The Masset for Google Drive Integration is meant to make it easy to bring your existing content into Masset. Masset does not use your Google Drive files or data to train or fine-tune any AI models.

Where can I submit feedback?

We love hearing from our customers and users. If you have questions, feedback, or want help with setup, reach out to support@getmasset.com. If you prefer to have a live feedback session where you can talk to us on a call, we’d love to do that too.