> 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/integrations/document-management/google-drive.md). # Google Drive With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Google Drive and, when **Write** access is enabled, perform approved actions in Google Drive. Connect Google Drive when client source documents, workpapers, or completed deliverables live in Google Drive or a Google shared drive. Filed uses the permissions already assigned to the Google account you authorize; it does not gain access to content that account cannot open. ## Before you connect Choose the Google account deliberately. It should be a firm-managed account that can access the client folders and shared drives that your team expects Filed to use. Before starting, confirm the account can: * Open the relevant Google Drive folders and files in the browser. * Access any shared drives used for client work. * Create or edit files in those locations if you intend to allow write actions. * Complete your firm's Google Workspace sign-in and multi-factor authentication requirements. If your firm uses Google Workspace, ask an administrator whether the Filed Google OAuth application has been approved. Workspace policy can block a consent screen even when the user has access to the files. ## Create the connection 1. Go to **Plugins & integrations** and select **Google Drive**. 2. Give the connection a clear name. Include the team, entity, or Drive scope when useful, such as `Tax Team Shared Drive` or `Smith CPA Google Drive`. 3. Review the connection permissions: * **Read** is always enabled and allows Filed to retrieve information from the Drive content available to the authorized account. * **Write** is enabled by default. Clear it if Filed should only read documents. You can change this later in the connection settings. 4. Select **Continue** to open Google sign-in. ## Authorize Google 1. Sign in with the intended Google account. If the account chooser shows a personal account, choose **Use another account** instead of proceeding with the wrong identity. 2. Review the permissions Google displays. These permissions let Filed work with the Drive files available to the selected account. 3. Select **Allow** to complete authorization. 4. Return to Filed and wait for the connection status to change to **Active**. The Google account, Google Workspace policies, shared-drive membership, and individual folder sharing rules all continue to govern what the connection can access. ## Verify the connection After the connection is active, use a known non-sensitive client folder to verify that Filed can see the expected documents. If your workflow needs to create or organize files, test that behavior in a safe folder before enabling write access for production work. For shared drives, verify that the connected account is a member of the drive itself. A folder link alone is not always enough to grant access to all expected content. ## Manage write access Turn off **Write** in the connection settings to make the connection read-only. Filed can continue to retrieve information from authorized Drive content, but it cannot run capabilities that create, upload, move, rename, or delete Drive content. Use read-only access when Filed is used for document review, search, or context gathering. Enable write only when your firm has approved Filed to modify Drive data. ## Reconnect or remove the connection Use **Reconnect** when Google access was revoked, the account password or multi-factor setup changed, or the connection shows pending or failed. Reconnect with the same intended firm account unless your firm is intentionally changing the ownership of the connection. Use **Remove** only when the connection should no longer be available in Filed. Removing it does not delete any files from Google Drive. ## Troubleshooting ### Google blocks the consent screen Your Google Workspace administrator may need to approve the OAuth application or requested scopes. Send the administrator the exact message shown by Google; do not bypass the policy by connecting a personal Google account. ### The wrong Google account was authorized Remove the pending or active connection and create a new one. Sign out of Google first, or choose **Use another account** at the Google account picker. ### A shared drive or folder is missing Open the folder in Google Drive as the authorized user. If it is unavailable there, Filed cannot access it either. Add the user to the shared drive or share the folder with that account, then reconnect or retry the operation. ### Filed can read files but cannot change them Check the connection's **Write** setting first. If Write is enabled, confirm that the Google account has Editor-level access to the target folder and that the folder is not restricted by shared-drive policy. ### The connection becomes failed after working previously The Google authorization may have been revoked, the account may have lost access, or Workspace policy may have changed. Select **Reconnect**, complete Google authorization again, and verify access to a known folder. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Google Drive information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Google Drive data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the Google Drive folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. --- # 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/integrations/document-management/google-drive.md?ask=&goal= ``` `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.