For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
      • ServiceNow (KB Only) Access Requirements
      • Sharepoint Online Access Requirements (KBs & Files) [Classic]
      • SharePoint (On-Prem) Access Requirements
      • Confluence Cloud Access Requirements
      • Confluence Server / Data Center Access Requirements
      • Google Drive Access Requirements
      • Notion Access Requirements
      • Guru Access Requirements
      • Salesforce Knowledge Access Requirements
      • Simpplr Access Requirements [NEW]
      • LumApps Access Requirements
      • Unily Access Setup Guide
      • Jive Access Requirements
      • Interact Access Requirements
      • Igloo Access Requirements
      • Haystack Access Requirements
      • GitHub Knowledge Access Requirements
      • Dropbox Content Access Requirements
      • Contentful Access Requirements
      • Quip Access Requirements
      • Slite Access Requirements
      • ScreenSteps Access Requirements
      • RightAnswers Access Requirements
      • SAP Build Work Zone Access Requirements
      • StaffBase Access Requirements
      • Squiz KB Access Requirements
      • WordPress Access Requirements
      • Workday Access Requirements (Knowledge)
      • Axero Access Requirements
      • Comaround Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • 1. Create Google Cloud Project and Grant Scopes to Moveworks Project
  • 1. Create Google Cloud Project
  • 2) Grant SDK and API Scopes to Project
  • 2) Create a Service Account and Save Service Account Key
  • 3) Create and Assign a Custom Admin Role for Reading Groups/Users
  • 4) Share Desired Google Drive Folders with Service Account
  • 5) Configure The Google Drive Connector in Moveworks Setup
Access RequirementsKnowledge Access Requirements

Google Drive Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Notion Access Requirements

Next
Built with

Note: This document describes the option available to create a Service Account with Custom Admin privileges, dedicated for Moveworks to ingest your Google Drive files, users, and groups for permission-enforced File Search.

This guide outlines how to create a Service Account with Custom Admin privileges and is the recommended approach for Google Drive

Alternative Connector Options are supported but not recommended:

  • Google Drive Service Account With Domain Wide Delegation
  • Google Workspace User with Custom Admin Role

1. Create Google Cloud Project and Grant Scopes to Moveworks Project

1. Create Google Cloud Project

  1. Create a Google Cloud Project for Moveworks
    1. Sign into https://console.cloud.google.com/cloud-resource-manager using an account with Google Workspace Super Admin privileges
    2. Click +Create Project
    3. Name the project Moveworks and select the top-level organization OU for your Google Workspace
    4. Click Create
    5. Once completed, click Select Project from Notifications or via Search

2) Grant SDK and API Scopes to Project

  1. Turn on the Admin SDK and Google Drive APIs for your Google Cloud Project
    1. From the top-left Navigation Menu, click APIs & Services > Enabled APIs & Services.
    2. Click +Enable APIs & Services.
    3. Search for each of the following APIs, and select Enable:
      • Admin SDK
      • Google Drive API

2) Create a Service Account and Save Service Account Key

  1. Navigate to APIs & Services > Credentials

  2. Select Create Credentials > Service Account

  3. Create the Service account by adding the name, ID and description and select Create and Continue - Note: Granting access to a project or Granting users access to this service account is optional

  4. Click on Actions > Manage keys

  5. Select Add Key > Create new key

  6. Select JSON as the Key type and click Create. You should see a notification that the service account JSON file has been downloaded and saved to your computer.

  7. Save this Service Account JSON Key

Get and Save Customer ID for your Google Workspace

  1. Follow the instructions here to grab the Customer ID:
    1. Go to Admin Console, select Account → Account Settings → Profile
    2. Save the Customer ID
    3. Instructions here at: https://support.google.com/a/answer/10070793?hl=en

3) Create and Assign a Custom Admin Role for Reading Groups/Users

  1. Create a Custom Admin Role, via these instructions here from Google
    1. Navigate to Google Admin Console, and create a new Admin Role
    2. Select the following privileges to assign to the Role
      1. Users → Read Users
      2. Groups → Read Groups
    3. Create the Role
    4. Assign the new custom admin role to the Service Account you created in Step 2 Above, by following the steps here.

4) Share Desired Google Drive Folders with Service Account

  1. In this step, make sure that each Google Drive Folder you wish to ingest as well as it’s parent shared drive has been shared with the new Service Account with Custom Admin privileges that you have built in previous steps.


  2. Add the Service Account as Content Manager. If your preference is to only grant Viewer access, please make sure that you have edited the following Shared Drive setting, allowing Viewers to download files:

5) Configure The Google Drive Connector in Moveworks Setup

  1. Navigate to Moveworks Setup and click on “Built in connectors”

  2. Create a new Google Drive connector

  3. Select Service Account Auth

  4. Open the JSON Key text file from Step 2 and copy the content of the “private_key”

  5. Open a new text file and paste the private key. Make sure new line characters, if applicable, are replaced with new lines. Once formatted correctly save the file as a .pem file type.

    1. The formatting show look similar to the below:

  6. Upload the .pem file from the previous step in the Gdrive Service Account Auth Private Key field.

  7. Leave “Impersonated User” as blank, given there is no Domain Wide Delegation