Skip to main content
Google Drive Integration

Connect your cloud storage to collect any file from Google's file storage platform as evidence

Micah Spieler avatar
Written by Micah Spieler
Updated today

With our Google Drive integration, you can attach files to evidence directly from your Google Workspace. Using a centralized storage location like Google Drive means helps increase efficiency (one less step in collecting evidence), data security (no need to download sensitive files onto your desktop first), and reduce clutter (collect directly from the single source of truth).

Types of evidence might you store in Google Drive

You can store almost any type of evidence in Google Drive and using a centralized storage system like Drive may help you keep your evidence organized as you're collecting it. Google Drive is also especially useful for storing policies and process documentation.

  • Approved policies & process documentation

  • Screenshots of file settings

  • HR documents like onboarding plans or employment records

Follow the instructions on this page to get started collecting evidence from Google Drive.

Step 1: Configure the integration

Since this integration connects directly with your Google account, each user who would like to collect evidence using Google Drive will need to configure the integration for themselves.

  1. Go to the Integrations Manager and click on the Google Drive card to access the integration configurations. Note: If you do not see Integrations Manager in your main navigation, you may not have access to this feature.

    1. If other users in your organization have already connected their Google Drive, you will see a list of configured integrations.

    2. To configure your own integration, press the "Add Another" button or "Connect Google Drive" button.

  2. Completed the authentication steps to connect with your Workplace Google account (make sure you use the same account that you use to log in with to Strike Graph).

  3. You will be redirected back to Strike Graph, and the integration should be complete! You can verify this by ensuring that your account is listed in the expanded Google Drive card.

Step 2: Using Google Drive to attach files to evidence

Once you have activated a Google Drive integration for your account, you can use it to attached files directly from your Google Drive to your evidence items.

Attaching a single file

This method is recommended for files that are regularly or continuously updated, for instance a policy document, asset list, etc.

  1. Open the evidence where you want to attach a file

  2. Click on the "Add Attachment" or "Automated Collection" button to open the attachment modal

  3. In the attachment modal, select the integrations tab and then select your Google Drive integration from the list

  4. This opens the Google Drive File Picker where you can browse your files and Shared Drives; click on your file and click on "Select"

Attaching the most recently modified file from a folder

If you create new versions of a file when making updates, you can also use this method to collect the most recently modified file from a folder in Google Drive. This is especially useful when paired with Automated Collection.

  1. Open the evidence where you want to attach files to

  2. Click on the "Automated Collection" button or the "Attach Directly" option

  3. In the attachment modal that opens, select the integrations tab and then select your Google Drive integration from the list

  4. Use the Google Drive File Picker to navigate to the folder that you want to collect from.

  5. Select the folder, and then click "Select" — this will then pull the most recently modified file inside of that folder and attach it to the evidence item. Note: If you don't have the option to select folders, please review the troubleshooting tips below.

Supported file types

We support most file types, including Google’s own native files like Google Docs and Google Sheets (FYI: they are converted to non-Google files during upload).

  • Google Doc (converted to .docx during upload)

  • Google Sheet (converted to .csv during upload)

  • Google Slide (converted to .pptx during upload)

Removing your Google Drive integration

You can remove the integration at any time. Please note that removing an integration does not delete any files that were attached used during that integration. Removing an integration may also disrupt automated collection.

To remove:

  1. Go to the Integrations Manager and click on the Google Drive card to access the integration configurations.

  2. Click the "Deactivate" button next to your user name.

Note: You may have access to remove integrations for other users on your team.

Using Google Drive with Automated Collection

With Automated Collection, Strike Graph can recollect evidence attachments from Google Drive a few days before expiration so that your evidence remains in an effective 'audit ready' state. More information is available here about configuring Automated Collection for your evidence.

For Automated Collection to work effective with Google Drive, it's helpful to understand how Google Drive keeps track and versions files that may be used as evidence.

Google Drive file versions

Google Drive assigns files a unique 'FileID' which is used by the integration and Automated Collection to during the collection process. This ID value needs to remain consistent for automated collection to know which file to recollection on a scheduled basis.

Depending on the type of file, Google Drive handles versioning differently, so as you are updating or adding new evidence to your Google Drive for eventual collection, take note of how versioning is handles for the type of file you're using to ensure that the automation continues to function as expected.

Google Native files (like Google Doc, Google Sheets, Google Slides, etc)

Files that are native to the Google Drive ecosystem work well with automated collection. When a new file is created, it is assigned a unique FileID, and that file ID remains consistent even if you move or rename the file.

If you make updates to the document, make sure to edit the file directly. Do not make a new copy of the file, because this will assign a new FileID and Automated Collection will continue to fetch the old file.

Making changes to the document directly is also helpful because Google Drive automatically creates versions and stores edit history, which is helpful if you need to rollback or track changes. Learn more about Google Drive's change history logs.

Non-native editable documents (like MS Word, MS PowerPoint, MS Excel, Apple Pages, Apple Keynote, or Apple Numbers files)

Static files can also be saved in Google Drive and be made available for Automated Collection. When files are added to Google Drive, Google provides each file with a unique FileID. If new versions of the file are added to Google Drive in the same location with the same file name, they will be added as a new version of the same FileID and will be available for the next recollection.

Troubleshooting

If you're having trouble with the Google Drive integration, check below for troubleshooting tips. If your issue is not resolved by the advice below, send us a message.

Can't select a folder for most recently modified file collection

If you can't select a folder in the Google Drive File Picker, or if you get an error while trying to use the 'folder' collection method, you may need to refresh the permissions for your integration. To do this:

  • Navigate to the Integration Manager

  • Open the Google Drive expander

  • Click on the "Reconnect" button next to your user email address

Once you go through the new consent screens, you should be able to select files out of a folder in your Google Drive.

Browser Support

The Google Drive integration works best in Chrome, but is also supported in Safari, Firefox, and Microsoft Edge. Sometimes, browser-specific privacy settings can interrupt calls between Strike Graph and Google Drive and cause issues for users. See notes below for specific browser settings to check if you experience problems.

  • Safari privacy settings known to impact the Google Drive functionality

    • If 'Prevent cross-site tracking' is enabled, users typically cannot complete the authentication process. Disable this setting (Safari > Preference > Privacy) and try again.

    • Google Drive's authentication is typically handled in a temporary popup window. If pop-up windows are blocked, you may need to manually approve their use from the URL bar, or allow Strike Graph to use popup windows. Allow grc.strikegraph.com to open popup windows (Safari > Preferences > Websites > Pop-up Windows) and try again.

"The API developer key is invalid" error

If you encounter an error stating "the API developer key is invalid" when trying to attach evidence using Google Drive, make sure that any ad blockers you have on your browser are deactivated and try to re-upload the evidence.

503 errors during evidence attachments

If you encounter 503 errors when trying to attach evidence using Google Drive, sometimes this can be triggered if the integration configuration did not correctly granted Strike Graph the necessary access to the Google Drive account during initial set up.

How to Fix: Deactivate the integration from the Integrations Manager page, and then re-configure the integration again, paying close attention to this setting, making sure that it is enabled during configuration:

Questions?

Reach out through our chat feature for real-time Customer Success support 8 am - 5 pm PT Monday through Friday.

Did this answer your question?