# General Translation Integrations: Connection
URL: https://generaltranslation.com/en-US/docs/integrations/google-drive/reference/connection.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: Connect a project to Google Drive with a personal Google account or an Organization shared drive. Reference for Google Drive connection modes, scopes, and permissions.

The connection mode decides which identity the integration uses, which files it can browse, and who has to authorize it. Both modes are connected from **Project > Integrations > Catalog**.

## Overview [#overview]

| Topic | Description |
| --- | --- |
| [Access modes](#access-modes) | Personal account and Organization shared drive connections. |
| [Personal account](#personal-account) | OAuth authorization for files a user can open. |
| [Organization shared drive](#shared-drive) | Shared translation account managed by an Organization admin. |
| [Required Drive capabilities](#capabilities) | What the active identity must be able to do in Drive. |
| [Plan and permissions](#gating) | Requirements for connecting and translating. |
| [Switching modes](#switching) | When a project can change its connection mode. |
| [Disconnecting](#disconnecting) | What remains after credentials are removed. |

## Access modes [#access-modes]

| Mode | Identity | Available files |
| --- | --- | --- |
| Personal account | Each user authorizes their own Google account. | Google Docs and Google Slides that user can open. |
| Organization shared drive | One Organization translation account. | Google Docs and Google Slides in shared drives that include the translation account. |

The Dashboard asks which mode to use only when the Organization has a verified, active shared drive connection on a plan that includes shared drive access. Otherwise the project uses personal accounts.

## Personal account [#personal-account]

Each user clicks **Connect account** on the integration's management page and completes Google authorization. The integration requests:

- `openid`
- `https://www.googleapis.com/auth/drive`

The full Drive scope lets the integration reach a document opened from the Google Docs or Google Slides add-on as well as files selected through the Dashboard. The integration translates only supported files you choose or explicitly open through those surfaces.

Connections created before this scope change can retain the narrower `https://www.googleapis.com/auth/drive.file` grant. They continue to work for files selected through the Dashboard, but the integration asks you to reconnect before it can translate another document opened from an add-on. A connection is usable only when Google returns a supported Drive scope together with a refresh token.

## Organization shared drive [#shared-drive]

An Organization admin sets this connection up once from **Organization > Connections**: click **Add connection**, then **Set up** for Google Drive. The Dashboard provisions a translation account and displays its email. Add that email to each permitted shared drive as a **Content manager**, then return to the Dashboard and click **Verify access**.

The translation account uses the `https://www.googleapis.com/auth/drive` scope so it can browse its configured shared drives. A project can select this mode only while the connection is **Active**.

Files added in this mode must live in a shared drive. Files in **My Drive** are rejected.

## Required Drive capabilities [#capabilities]

Whichever identity is active must be able to:

- Read and copy each source Google Doc or Google Slides presentation.
- Create the translated copy alongside the source file.
- Edit that copy on later runs.

If the source cannot be copied, that file and language fail while the rest continue. A translated copy that is readable but not editable also fails, because the integration stops rather than creating an unrelated duplicate. If the recorded copy has been deleted or moved to trash, the integration treats it as stale and creates a replacement on the next run.

## Plan and permissions [#gating]

| Action | Permission | Plan |
| --- | --- | --- |
| Connect the project integration | `project:write` | Starter or Enterprise |
| Connect or reconnect a personal Google account | `translations:content:write` displays the Dashboard controls; `project:files:write` and `project:translations:enqueue` authorize the connection | Starter or Enterprise |
| Add, remove, or translate files in the Dashboard | `project:files:write` and `project:translations:enqueue` | Starter or Enterprise |
| Configure an Organization shared drive | `org:manage` | Enterprise |

Without the project integrations feature, the catalog shows an upgrade prompt in place of the connection controls. Without the required permission, the corresponding action is unavailable.

The [Google Drive MCP tools](/docs/integrations/google-drive/reference/mcp-tools) use project file and translation-queue permissions instead of the Dashboard translation-content permission.

## Switching modes [#switching]

A project cannot switch from an Organization shared drive to personal accounts while shared drive files are still linked. Remove those files first, then reconnect the integration with personal access.

## Disconnecting [#disconnecting]

- **Disconnect account** removes one user's stored Google credentials. The project keeps its linked files, but that user cannot translate them until they reconnect. Other members keep access through their own accounts.
- **Disconnect** on the Organization connection removes the shared drive translation credentials. Projects using it lose Drive access until an Organization admin configures it again.

Neither action deletes source files or translated copies from Google Drive. Removing a linked file from the integration also leaves both untouched in Drive.

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.