Skip to main content
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.
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.

​
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.
1

Choose file access deliberately

Google’s Drive scope guide 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.
2

Record the source and permitted content

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

Review the copy's lifecycle

If you import an approved export through knowledge document management, 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.
Keep Google token handling in the authorized integration service. A manual auth connection does not supply a Google consent flow. For a future on-demand fetch, review the tool contract and report inaccessible or stale sources explicitly.

​
Frequently asked questions

No verified synchronization exists. Review and replace imported content through the knowledge workflow when its source changes.
This guide covers selected documents. Bulk enumeration, permission propagation, and deletion synchronization need separate implementation and access review.