Wevion owns a per-user Drive folder via a Service Account and grants your Gmail writer access. No personal OAuth; you work directly in the Wevion-owned folder.

Connect Google Drive

Wevion connects to Google Drive via a Service Account (NOT user OAuth — verified in apps/backend/src/lib/google-drive.ts). The service account uses GOOGLE_SERVICE_ACCOUNT_EMAIL + GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY env vars with scope https://www.googleapis.com/auth/drive. Wevion creates and owns a folder for you and grants your Gmail writer access to it. You do not share your own folder with Wevion — instead you get writer access to the Wevion-owned Creative Hub folder.

Who is this for

Creatives and mediabuyers who want to:

• Access their Creative Hub files directly in Google Drive
• Collaborate on Creative Hub assets with teammates via Drive
• Work with Creative Hub files using native Drive tools

How Drive access works

Most Wevion integrations use user OAuth (you authenticate your Meta/Google Ads/Shopify account). Drive is different, and the direction is the opposite of what people expect:

• Service Account model: Wevion has a server-side service account with its own Google identity (apps/backend/src/lib/google-drive.ts)
• Wevion creates and owns a per-user Drive folder for your Creative Hub files (ensureUserFolder in apps/backend/src/services/creative-hub/creative-hub.helpers.ts)
• You grant your Gmail writer access to that Wevion-owned folder via /connect/google-drive
• Wevion then shares its folder with your email (role: 'writer') — you never share a folder of your own with Wevion

Benefits:

• No browser OAuth flow needed
• No token expiry (service account credentials managed by Google)
• Wevion owns the folder, so Creative Hub stays the source of truth
• You (and teammates you authorize) can open the same files directly in Drive

Before you start

• A Google account (the Gmail address you want to grant Drive access to)
• Wevion role: manager, admin, owner, super_admin

How to connect

Step 1: Open the Drive connector page

In sidebar click Connect → Google Drive or visit /connect/google-drive. The page lists the emails currently authorized to access your Wevion Creative Hub folder (GET /api/v1/creative-hub/shared-emails), with an add / remove control.

Step 2: Grant your Gmail access

Enter the Gmail (or Google Workspace) address you want to authorize and confirm. Wevion:

1. Ensures your Wevion-owned Creative Hub folder exists (creating it via the service account if needed)
2. Grants that email writer access to the folder (POST /api/v1/creative-hub/share, role: 'writer')

There is no "share your own folder with Wevion" step — Wevion owns the folder and shares it with you.

Step 3: Open the folder in Drive

The authorized Gmail account receives writer access to the Wevion-owned folder. Open Google Drive with that account — the folder appears under Shared with me. Files you and Wevion place there are visible to both.

Step 4: Revoke access when needed

To remove an email's access, use the remove control on /connect/google-drive (POST /api/v1/creative-hub/unshare). That email loses access to the Wevion-owned folder.

Service Account details

Wevion's service account (ID format [name]@[project].iam.gserviceaccount.com) owns the Creative Hub folders and is what grants your email access — you don't need to enter it anywhere.

If env vars are not configured (GOOGLE_SERVICE_ACCOUNT_EMAIL or GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY missing), the Drive connector returns an error: "Google Drive credentials not configured." Contact support@wevion.ai to enable.

What access you get

When you authorize an email, Wevion grants it writer access to the Wevion-owned Creative Hub folder (role: 'writer', type: 'user'). Writer means that account can view, add, and edit files in that folder directly from Drive.

What's accessible

The authorized account can access, from Drive:

• The Wevion-owned Creative Hub folder (and its contents) that was shared with your email
• File metadata + content for files in that folder

The authorized account does not get access to:

• Any Wevion data outside your Creative Hub folder
• Other users' Creative Hub folders
• Wevion's Gmail, Calendar, or any other Google service

Note the direction: Wevion (via its service account) owns the folder; you receive access to it. Wevion does not read your personal Drive.

Use cases

Drive access to Creative Hub files

Most common use: authorize your Gmail so you can open your Creative Hub folder directly in Drive — view, add, or edit assets with native Drive tools. Changes are made in the same Wevion-owned folder Creative Hub uses.

See com-113 for folder management.

Team collaboration on assets

Authorize teammates' Gmail addresses so several people can work on the same Creative Hub folder in Drive. Each authorized email gets writer access; remove access at any time from /connect/google-drive.

Multiple authorized emails

You can authorize more than one email for your Creative Hub folder — for example yourself plus a designer or an external collaborator. Each is granted writer access to the same Wevion-owned folder; the list of authorized emails is shown at /connect/google-drive.

Removing access

To revoke an email's access:

1. In Wevion: /connect/google-drive → remove the email (POST /api/v1/creative-hub/unshare)
2. That account immediately loses access to the Wevion-owned folder

The folder and its files stay in Wevion (Wevion owns them); only the external access is removed.

Security

• Service account private key stored encrypted at rest in Wevion's secret manager
• Wevion owns the Creative Hub folder; authorized emails get scoped writer access to that folder only (Google enforces at Drive API level)
• Wevion does not read your personal Drive, Gmail, or other Google services

What you'll see

After authorizing an email:

• /connect/google-drive lists the authorized email
• That Gmail account sees the Wevion-owned Creative Hub folder under Shared with me in Drive
• A success toast confirms access was granted

Common issues

• "Drive credentials not configured": env vars (GOOGLE_SERVICE_ACCOUNT_EMAIL / GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY) missing on Wevion's backend. Contact support.
• Authorized but folder not visible in Drive: check the Shared with me section in Drive for the exact Gmail you authorized; confirm the address was entered correctly.
• Wrong Gmail authorized: remove it from /connect/google-drive and add the correct one.
• Email rejected: format issue — enter a valid Gmail / Workspace address and retry.

FAQ

How does Wevion connect to Google Drive?

Wevion connects via a Google Service Account, not user OAuth. Wevion owns a per-user Creative Hub folder created by that service account, and grants your Gmail writer access to it. You do not share a folder of your own with Wevion — instead you receive access to the Wevion-owned folder. This means no browser OAuth flow and no token expiry.

Can Wevion see my entire Google Drive?

No. The relationship is the reverse of that: Wevion owns the Creative Hub folder and shares it with your email. Wevion does not read your personal Drive, other users' files, or any other Google service such as Gmail, Calendar, or Contacts. The authorized email only gets access to the specific Wevion-owned folder.

What access does the authorized email get?

Wevion grants writer access (role: 'writer') to the Wevion-owned Creative Hub folder, so that account can view, add, and edit files in that folder directly from Drive. Access is scoped to that one folder only.

How do I authorize or revoke Drive access?

Go to /connect/google-drive, which lists the emails currently authorized for your Creative Hub folder. Add an email to grant it writer access (POST /api/v1/creative-hub/share), or remove one to revoke access (POST /api/v1/creative-hub/unshare). Revoking removes only that account's access — the Wevion-owned folder and its files remain in Wevion.

Related articles

• Drive creative folder management
• Upload your first creative to Creative Hub
• All integrations — overview and use cases