Skip to main content

Instructor, no.

Incydr Professional, Enterprise, Gov F2, and Horizon, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, no.

CrashPlan for Small Business, no.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

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:
    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.

...

File events aren't appearing for a shared drive

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Google_Drive), /content/body/div/ins/span, line 1, column 10
monitors a shared drive only when at least one of its members is an in-scope user. If file events aren't appearing for a shared drive as expected, examine the list of people or groups who have been assigned to that drive. Then, use one of these methods to adjust that user list as needed:
  • In
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Google_Drive), /content/body/div/ul/ins[1]/span, line 1, column 10
    
    ,
     reconfigure scoping in
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Google_Drive), /content/body/div/ul/ins[2]/span, line 1, column 10
    
    to add one or more members of that drive as users that are in scope for monitoring.
  • In Google Drive, add a user that is in scope for monitoring as a member of that shared drive.

...

Other changes:

  1. /body/ol/li[2]/ol/li[4]/img/@src:
  2. "/@api/deki/files/33013""/@api/deki/files/34091/1_GoogleDrive_add_connect_2021-06-24.png"
  3. /body/ol[2]/li[2]/img/@alt:
  4. "Add Google Drive users""Add users"
  5. /body/ol[2]/li[2]/img/@src:
  6. "/@api/deki/files/33014""/@api/deki/files/34092/2_GoogleDrive_add_users_2021-06-24.png"
  7. /body/ol[3]/li/img/@src:
  8. "/@api/deki/files/33015""/@api/deki/files/34093/3_GoogleDrive_verify_email_2021-06-24.png"
  • Was this article helpful?