> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/document-management/google-drive.md).

# Google Drive

## What this integration does

The Google Drive integration gives Filed direct access to client documents stored in Drive, without manual uploads. You designate one Drive folder as the root; sub-folders inside it map one-to-one to client records in Filed. Once a client is imported, Filed can read, organize, and write files within that client's Drive folder, so your team can file documents back to Drive directly from Filed.

During the connection flow, Filed requests these Google OAuth scopes:

* Full Drive access (`drive`)
* Your account email address (`userinfo.email`)
* Basic identity (`openid`)

These permissions let Filed list, find, download, upload, copy, move, rename, and delete files, and create folders on your behalf.

## Before you start

You need a Google account that has access to the Drive folder containing your client sub-folders. The top-level folder must be organized with one sub-folder per client at the immediate first level. You must be able to complete the Google sign-in and consent screen during the connect flow.

## Connecting Google Drive to Filed

{% embed url="<https://player.vimeo.com/video/1146062198?h=68780a53f1>" %}

{% embed url="<https://scribehow.com/embed/How_to_connect_Google_Drive_to_Filed__f-aOM7rDTBC0IUTHnjI8CQ?removeLogo=true&as=scrollable>" %}

## Importing clients from Google Drive

## What Filed can do with Google Drive

Once connected, Filed exposes the following actions against your Drive:

**Reading and finding files**

* List the contents of any folder
* Find a file or folder by name or search query
* Download a file's content

**Organizing files**

* Copy a file to another folder
* Move a file to a different folder
* Rename a file or update its metadata (description, name)
* Delete a file or folder

**Creating content**

* Create a new folder
* Upload a document into a folder (files up to 5 MB; larger files use Google's resumable upload protocol automatically)

These actions are what power binder creation and update: when Filed prepares a client's binder, it uses this set of capabilities to retrieve source documents from Drive and to file completed documents back.

## Troubleshooting

**Connection error on the DMS page.** Disconnect the integration and reconnect. Verify that the Google account you used still has access to the folder you originally selected. If your firm uses Google Workspace, check with your Google administrator to confirm that the account has not lost access to that folder.

**Clients are not appearing after import.** The top-level folder you selected must contain sub-folders at exactly one level deep, one per client. Nested folder structures or files at the top level are not treated as client records. If the folder structure does not match, reconnect and select the correct folder.

**Documents are not available in the binder.** Allow a few moments for Filed to fetch the files. If files are still missing, open the client record and trigger a re-sync from the client hub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.filed.com/reference/plugins/document-management/google-drive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
