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

# Connect Google Drive

> Claim and verify a client-owned creative folder for read-only Launcher inventory sync.

Launcher connects to client-owned Google Drive folders through a read-only service account. PlainRouter verifies ownership before it inventories any media, so knowing a folder link is never enough to claim another workspace's creative library.

<Info>
  This release inventories Drive media metadata only. It does not download media bytes, upload media to Meta, create ads, or activate spend.
</Info>

## Before you begin

You need:

* Workspace-owner access in PlainRouter.
* A verified email address on your PlainRouter account.
* Permission to share the intended Google Drive folder.
* A Launcher service-account email on the workspace settings page.

If **Drive access is not provisioned for this workspace cell yet** appears, contact PlainRouter support before continuing.

## Connect a folder

<Steps>
  <Step title="Open workspace settings">
    In the PlainRouter sidebar, open **Account** → **Workspace**. Find **Launcher Drive access**.
  </Step>

  <Step title="Share the folder">
    Copy the displayed service-account email. In Google Drive, add that address to the intended folder as a **Viewer**.

    Share a top-level folder when you want Launcher to include its subfolders.
  </Step>

  <Step title="Submit the folder link">
    Copy the folder's HTTPS Google Drive link into **Google Drive folder link**, then click **Claim folder**. PlainRouter starts ownership verification and reserves the claim for 72 hours.
  </Step>

  <Step title="Complete ownership verification">
    PlainRouter first attempts owner-domain verification. If the page presents a challenge filename, create an empty file with that exact name directly inside the claimed folder. Return to PlainRouter and click **Verify ownership**.
  </Step>

  <Step title="Wait for the verified state">
    The folder becomes **Verified** only after ownership proof succeeds. PlainRouter then starts the first read-only inventory sync automatically.
  </Step>
</Steps>

## How ownership verification works

| Situation                                                                                                                                   | Verification path                                                                                                         |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| The folder is not link-public, Drive exposes its owners and permissions, and an owner domain matches your verified PlainRouter email domain | PlainRouter verifies the claim automatically with **Domain** verification.                                                |
| The owner domain differs or Drive does not expose enough owner or visibility metadata                                                       | You must use the challenge file shown in workspace settings.                                                              |
| The folder is available to anyone with its link                                                                                             | Challenge-file verification is always required, even when the owner domain matches.                                       |
| The folder is already verified by another workspace                                                                                         | PlainRouter rejects the claim. A verified folder can belong to only one workspace.                                        |
| Another workspace has an unverified claim                                                                                                   | The claim remains reserved until its 72-hour verification window ends. An expired unverified claim can then be reclaimed. |

The challenge file must use the exact generated `verify-<token>.txt` filename. Put it directly inside the claimed folder, not in a subfolder. Workspace members can view claim state, but only the workspace owner receives the challenge filename or can manage the connection.

## What Launcher syncs

After verification, Launcher scans the folder and its subfolders every 15 minutes. Shared Drive folders are supported.

The current read-only inventory recognizes:

* GIF, JPEG, and PNG images.
* MP4 and MOV videos.

Launcher records file identity, name, type, size, checksum, and modified time. Unsupported files are ignored. Unchanged files are skipped idempotently, changed metadata is reconciled, and files missing from a complete scan are marked removed.

Each sync attempt and outcome is recorded as durable operational evidence. Folder claims and ownership results also enter the workspace's [v2 audit chain](/docs/actions/audit-log).

## Connection states

| State                       | Meaning                                                                                                    |
| --------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Claimed unverified**      | Verification is still running or needs a challenge file. No inventory sync can run.                        |
| **Failed**                  | Ownership proof did not succeed. Follow the displayed guidance and retry before the claim expires.         |
| **Expired**                 | The 72-hour ownership claim ended without verification. Submit the folder link again to start a new claim. |
| **Verified**                | Ownership proof succeeded and read-only inventory sync is enabled.                                         |
| **Verified · disconnected** | Ownership remains verified, but Google Drive no longer allows the service account to read the folder.      |

## Troubleshoot

### Challenge file not found

Confirm that the file uses the exact displayed name and sits directly inside the claimed folder. Make sure the service-account email still has **Viewer** access, then click **Verify ownership** again.

### Folder inaccessible

Google Drive returned an access denial or could not find the folder. Re-share the folder with the displayed service-account email. For a previously verified folder, click **Retry sync**. You do not need to repeat ownership verification.

### The link is rejected

Submit an HTTPS link to a Google Drive folder, not a file. Open the folder in Drive and copy its browser URL.

### The folder is claimed by another workspace

A verified folder cannot be connected to two workspaces. Switch to the workspace that owns the existing connection. If the other claim is unverified, retry after its 72-hour window ends.

### Verification keeps failing

Use the challenge-file path when the Drive owner uses another email domain, the folder is link-public, or Drive does not expose enough sharing metadata for automatic domain verification.

## Next step

After inventory sync finishes, [import a Launcher draft batch](/docs/launcher/import-draft-batch) from CSV or XLSX, or pass the synced Drive links directly to `launcher.draft_batch` through MCP.