Resolve Google Drive security data errors
Overview
In certain situations, Code42 may be unable to access your Google Drive environment to monitor its file activity. When Code42 is unable to gather data from your Google Drive environment, the following message appears at the top of the Data Connections screen after the Google Drive connection is authorized:
Data connection <ConnectionName> is not sending security data. To correct the problem, deauthorize then resume monitoring.
This article tells you how to resolve the error.
Resolve the "not sending security data" error
To resolve this issue, try the following solutions in the order listed:
- Make sure that your Google Workspace administrator has the Super Admin role.
- If needed, update permissions in the Google Admin console to give your administrator the Super Admin role.
- After updating administrator permissions, deauthorize the Google Drive cloud storage data connection in the Code42 console.
- Resume monitoring the Google Drive cloud storage data connection again using the email address of the administrator with the Super Admin role.
The authorization process must be completed by someone who holds the Super Admin role in your Google Workspace. No other administrator levels are valid.
- Verify that the permissions (or scopes) required by the Code42 service account have been added to your Google Workspace correctly.
- Verify that Drive and Docs is turned on for everyone in your Google Workspace (or for everyone in the Google Workspace organizational unit that you want to monitor).
Code42 can only monitor file activity for the organizational units with Drive and Docs enabled. - Verify that third-party apps have access to Drive files. Code42 cannot monitor your Google Drive environment if this setting is disabled.
External resources
- Google: Turn Drive on or off for users
- Google: Allow third-party apps for Drive files