> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Drive

> Prepare selected-document access and knowledge import with explicit permissions, provenance, and removal rules.

Plan a workflow that reads one approved Drive document for a knowledge source. Decide whether your application needs a temporary excerpt or a separately stored copy.

<Note>
  There is no native Google Drive connector, Google file picker, or continuous Drive synchronization in the reviewed Threetone implementation. Existing knowledge import is a separate workflow.
</Note>

## Prepare a document import

You need the document owner's approval, a known file ID, and an application that owns Google authorization and any export operation.

<Steps>
  <Step title="Choose file access deliberately" id="google-drive-permissions">
    Google's [Drive scope guide](https://developers.google.com/workspace/drive/api/guides/api-specific-auth) recommends narrow per-file access where appropriate. The `drive.file` scope covers files opened or shared with the app and can permit changes; it is not universal read-only access. Review the scope, app behavior, and selected files together.
  </Step>

  <Step title="Record the source and permitted content" id="google-drive-source">
    Preserve the file ID, source URL, title, and version or modification evidence available to your application. Review document text before export. Exclude comments, linked files, or attachments unless separately approved.
  </Step>

  <Step title="Review the copy's lifecycle" id="google-drive-copy">
    If you import an approved export through [knowledge document management](/agents-platform/configure/knowledge-base/manage-documents), read the document and ingestion status back. Assign an owner for refresh and removal. Revoking Drive access does not automatically remove a copy previously uploaded to Threetone.
  </Step>
</Steps>

Keep Google token handling in the authorized integration service. A [manual auth connection](/agents-platform/configure/authentication/auth-connections) does not supply a Google consent flow. For a future on-demand fetch, review the [tool contract](/agents-platform/configure/tools/overview) and report inaccessible or stale sources explicitly.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Will changes to a Drive file update knowledge automatically?" id="faq-google-drive-sync">No verified synchronization exists. Review and replace imported content through the knowledge workflow when its source changes.</Accordion>
  <Accordion title="Can I import an entire shared drive?" id="faq-google-drive-bulk">This guide covers selected documents. Bulk enumeration, permission propagation, and deletion synchronization need separate implementation and access review.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.