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

# Importing From Cloud Drives

> Choose Google Drive files for Murph and creative upload workflows

## Overview

Cloud drive imports let a signed-in user choose files from cloud storage,
starting with Google Drive. They are designed for creative and operations work
where briefs, images, videos, and review materials already live in a shared
drive.

Google Drive is available directly from the Murph composer and campaign
creative upload workflow. It does not require a separate setup step in
Connections. Each import opens a Google-owned selection window where the user
authorizes and chooses the files for that import.

Cloud drives are separate from ad platform connections. Connecting Google Drive
does not grant Scope3 access to Google Ads, Google Ad Manager, a storefront, or
an ADCP sales agent. It only authorizes the cloud-drive file workflow for the
signed-in user.

## Google Drive

Scope3 requests file-scoped Google Drive access. Each selection happens in a
top-level Google window, so it works without third-party cookie access. Scope3
can work with files the user selects for Scope3 in a supported workflow, not
broadly index or manage the user's entire Drive.

The selected-file workflow does not create a persistent Google Drive
connection in Interchange. Google asks the user to authorize access in the
selection window each time files are added.

## What It Enables

Google Drive import lets a signed-in user:

* Choose files from Google Drive while bulk-uploading campaign creatives.
* Choose **Add from Google Drive** from the `+` menu in Murph and attach the
  selected files to a message.
* Preview, group, and validate imported files through the same workflow used
  for local files, folders, and zip archives.

To import campaign creatives, open the campaign's **Creative assets** view,
choose **Bulk upload**, and select **Google Drive**. Scope3 downloads only the
files selected in the Google-owned window and applies the normal creative file
limits.

In Murph, choose **Add from Google Drive** from the composer `+` menu. The
Google selection window opens without leaving the conversation, so the text
draft stays in place. Selected files become ordinary message attachments.

## Requesting Other Cloud Drives

**Connections → Cloud drives** lists curated cloud drives that are not available yet,
including Microsoft OneDrive, Dropbox, and Box. Choose **I want this** to record
your organization's interest. The request does not create a connection or
grant Scope3 access to that provider.

## What It Is Not Used For

A cloud drive connection does not:

* Connect an advertiser account or ad platform account.
* Keep ongoing access to a Google Drive account.
* Browse, index, map, or watch Drive folders in the background.
* Give Scope3 permission to manage users, sharing settings, or billing in
  Google Workspace.
* Turn Connections into a marketplace for arbitrary MCP servers.
* Authorize Scope3 to write generated files back to Drive unless a future
  workflow explicitly asks for that capability.

Persistent folder access, monitoring, and source-file mapping are not part of
selected-file import. A future sync workflow would require a separate,
explicit connection and broader read permission.