Wevion uses Drive Service Account (NOT user OAuth). Admin views connection status + service account email + total storage at /settings → Integrations.

Google Drive settings

Wevion's Creative Hub is backed by Google Drive via a Service Account (NOT individual user OAuth). All files are owned by the Service Account; visibility within Wevion is controlled by Wevion's RBAC (ch-109); external sharing is handled by Drive's permissions API (ch-105). Configured at workspace level — per-user OAuth is NOT available.

Who is this for

Admins setting up Wevion or troubleshooting Drive integration issues. Owners auditing the workspace's Drive setup.

The setup model

A Google Cloud project hosts a Service Account: an automated identity that Wevion uses to authenticate against Drive. The Service Account has its own Drive (Shared Drive) where Creative Hub files live.

Configuration:

• GOOGLE_SERVICE_ACCOUNT_EMAIL — env var with the service account's email
• GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY — env var with the private key for signing requests

Both are set at the Wevion deployment level (not in the UI). Workspace-wide; one service account per Wevion deployment.

Where to see it

/settings → Integrations → Google Drive shows:

For deeper setup walkthrough (env vars, Google Cloud project, Shared Drive), see com-113 Google Drive setup.

Why Service Account (not user OAuth)

Service Account trade-off: file ownership is the Service Account, not individuals. This means: users see files in Drive only if Wevion explicitly shared them (ch-105).

Admin actions

View status

Visit /settings → Integrations → Google Drive. Quick health view.

Trigger health check

Some Wevion versions show Re-check connection button. Calls Drive API; updates status badge.

View storage usage

Same page shows total + per-folder breakdown (top-level folders by size).

Rotate credentials

If service account credentials need rotation:

1. In Google Cloud Console: generate new private key for the service account
2. Update GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY env var in Wevion deployment
3. Restart Wevion services
4. Trigger health check

Coordinate with admin / DevOps — env var change requires deploy or restart.

Review shared files

Drive sharing is not written to the audit log (there is no creative_share audit action). To see who currently has access to a user's Creative Hub folder, use GET /api/v1/creative-hub/shared-emails.

Limits + quotas

• Drive quota: depends on Google Workspace plan (Shared Drive has separate quota from individual users)
• API rate limits: Drive API has per-project quotas; Wevion respects them with retry + backoff
• Files per folder: Drive's max is 500K but Wevion's UI degrades past 1K per folder — subfolder!
• Concurrent operations: per-second limits on Drive API; bulk operations queued

Troubleshooting

Connection status "Error"

• Service account credentials expired or rotated without env update
• Service account lost Drive permissions (someone in Cloud Console removed it)
• Drive API quota exhausted for the day (rare)

Action: check /settings → Integrations → Google Drive status detail; coordinate with DevOps to verify env vars + Cloud Console.

Quota near full

• Files accumulate; periodic cleanup needed
• Delete old _archive folder contents
• Or upgrade Drive storage in Google Workspace

File operations slow

• Drive API latency spike
• Or high concurrent load (many users uploading simultaneously)
• Usually resolves on its own

"Permission denied" on file operations

• Service account lost write permission to the Shared Drive
• Service account email changed in Cloud Console without env update

Action: verify Service Account email matches in env + Cloud Console.

Common mistakes

• Trying to configure Drive in Wevion UI: not possible — it's env-var-based (deployment level)
• Sharing Service Account credentials: never share the private key; treat as a secret
• Switching Service Account without migration plan: existing files will become orphaned (new SA can't see old SA's files); coordinate carefully
• Expecting users to see all files in their personal Drive: they only see what Wevion explicitly shared via ch-105

FAQ

Does Wevion's Creative Hub use my personal Google Drive account?

No. Wevion's Creative Hub is backed by Google Drive via a Service Account — an automated identity — not individual user OAuth. All files are owned by the Service Account in a Shared Drive, and per-user OAuth is not available. This means one auth for the entire workspace, no re-auth on token expiry, and no files counting against your personal Drive quota.

Where can admins check the Google Drive connection status?

Go to /settings → Integrations → Google Drive. Wevion shows the connection status (OK / Error from the last health check), the service account email, total storage used, quota remaining, and the last successful sync timestamp. Some versions also offer a Re-check connection button that calls the Drive API and updates the status badge.

Why can't I configure Google Drive from the Wevion UI?

Drive configuration is env-var-based at the deployment level, not editable in the UI. The GOOGLE_SERVICE_ACCOUNT_EMAIL and GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY variables are set on the Wevion deployment, one service account per deployment. Rotating credentials means generating a new key in Google Cloud Console, updating the env var, restarting services, then triggering a health check — coordinate with DevOps.

What does a "Connection status: Error" mean?

It usually means the service account credentials expired or were rotated without updating the env var, the service account lost Drive permissions in Cloud Console, or the Drive API daily quota was exhausted. Check the status detail at /settings → Integrations → Google Drive and coordinate with DevOps to verify the env vars and Cloud Console setup match.

FAQ

Does Wevion's Creative Hub use my personal Google Drive account?

No. Wevion's Creative Hub is backed by Google Drive via a Service Account — an automated identity — not individual user OAuth. All files are owned by the Service Account in a Shared Drive, and per-user OAuth is not available. This means one auth for the entire workspace, no re-auth on token expiry, and no files counting against your personal Drive quota.

Where can admins check the Google Drive connection status?

Go to /settings → Integrations → Google Drive. Wevion shows the connection status (OK / Error from the last health check), the service account email, total storage used, quota remaining, and the last successful sync timestamp. Some versions also offer a Re-check connection button that calls the Drive API and updates the status badge.

Why can't I configure Google Drive from the Wevion UI?

Drive configuration is env-var-based at the deployment level, not editable in the UI. The GOOGLESERVICEACCOUNTEMAIL and GOOGLESERVICEACCOUNTPRIVATE_KEY variables are set on the Wevion deployment, one service account per deployment. Rotating credentials means generating a new key in Google Cloud Console, updating the env var, restarting services, then triggering a health check — coordinate with DevOps.

What does a "Connection status: Error" mean?

It usually means the service account credentials expired or were rotated without updating the env var, the service account lost Drive permissions in Cloud Console, or the Drive API daily quota was exhausted. Check the status detail at /settings → Integrations → Google Drive and coordinate with DevOps to verify the env vars and Cloud Console setup match.

Last updated: 2026-05-17

Related articles

• Connect Google Drive
• Google Drive RBAC
• Share folder with external collaborators