Allow Code42 access to Google Drive

...

1. Return to the
   ParseError: EOF expected (click for details)

   Callstack:
       at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Google_Drive), /content/body/ol/li[1]/span, line 1, column 10
   

   .
2. In the Add Data Connection dialog, click Continue. 
   The Add Users panel displays.
   
3. Select one of the following options:
   • All
     Monitors all Google Drive users in your environment, including any drives owned by suspended users.
   • Specific Users
     Monitors only the Google Drive users you designate.
     1. Click Upload .CSV File.
     2. Select a .csv file containing a list of only those Google Drive users you want to monitor.
        For details, see  Upload a .csv file listing Google Drive users below.
   • Specific Groups
     Monitors only the users in Google Drive groups you designate.
     1. Click Upload .CSV File.
     2. Select a .csv file containing a list of Google Drive groups whose users you want to monitor. 
        For details, see Upload a .csv file listing Google Drive groups below.
   Monitoring of shared drives is dependent on in-scope users
   Code42 monitors a shared drive only when at least one of its members is also a monitored user. During initial indexing, Code42 scans the shared drives in your Google Drive environment to identify their members. Code42 then determines which of those members are also users that are monitored by the Code42 connection. (You identify the members that are in scope for Code42 monitoring when you authorize its connection to your Google Drive environment.) If no members of that shared drive are users that are monitored, Code42 does not monitor that shared drive.

...

• The .csv file is limited to 1,000 entries.
• Uploading a new .csv replaces the existing list of people or groups being monitored.
All Sharedshared drives are monitored if at least one member is an in-scope user.
Monitoring of shared drives is dependent on in-scope users
Code42 monitors a shared drive only when at least one of its members is also a monitored user. During initial indexing, Code42 scans the shared drives in your Google Drive environment to identify their members. Code42 then determines which of those members are also users that are monitored by the Code42 connection. (You identify the members that are in scope for Code42 monitoring when you authorize its connection to your Google Drive environment.) If no members of that shared drive are users that are monitored, Code42 does not monitor that shared drive.

...

Callstack:
    at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Google_Drive), /content/body/div/ins/span, line 1, column 10