Creative management & AI generation — complete guide

Creative Hub: upload, organize, share, AI generation (catalog 6 image + 6 video + 3 avatar + 3 TTS + 1 compositing; legacy /generate route exposes a subset), credits, permissions.

Written By Salvatore Sinigaglia

Last updated About 5 hours ago

Creative Hub: upload, organize, share, AI generation (catalog 6 image + 6 video + 3 avatar + 3 TTS + 1 compositing; legacy /generate route exposes a subset), credits, permissions.

Creative management & AI generation — complete guide

TL;DR: Wevion's Creative Hub = file library + AI generation. Storage: Google Drive Service Account (NOT user OAuth), with no creative_hub_file DB table (files live on Drive). Upload + organize + share + use in Campaign Creator + AI-generate. Provider catalog: 6 image / 6 video / 3 avatar / 3 TTS / 1 compositing; the legacy /generate/* route exposes only a subset. Async jobs via SQS workers. Credits are a separate ledger, and charging is gated by the creative_billing flag.

Table of contents

Creative Hub overview

/creative-hub. Asset library + AI generation studio.

Upload + organize files

Drag-drop OR Upload button. Supported: images (jpeg / png / webp / gif), video (mp4 / mov / webm), and documents (e.g. pdf). Creative Hub upload limit: 500 MB per file, up to 50 files per upload. (The 10 MB limit is for chat attachments, a separate flow.)

Share + collaborate

Drive permissions API for external sharing. role='writer' + type='user', applied at the folder level (shares your whole Creative Hub folder, not a single file).

Use in Campaign Creator

Pick Creative Hub file in cc-116 creatives block when building campaign.

AI generation overview

5 generation types. Provider catalog (per providers/creative/types.ts); the legacy /generate/* route exposes only the bolded subset:

TypeCatalog (route subset in bold)
Imagesseedream_4 (default), seedream_4_5, nano_banana_pro, nano_banana, flux_2_pro, gpt_image_1_5
Videosluma_ray3, runway_gen4, kling_2_6, kling_3_0, veo_3_1, seedance_pro
Avatarsheygen (route), kling_avatar, veed
Text-to-Speechelevenlabs, openai_tts, heygen
Video compositingcreatomate

Async via SQS workers. Poll via GET /api/v1/creative-hub/generate/jobs/:id.

Credits + limits

Metered on the credit_balance model (owner_id, balance, plus weekly-grant + monthly-cap fields), with cost_cents per generation. Charging is gated by the creative_billing flag, which ships OFF by default — with it off, standalone generations run without a credit hold or debit; with it on, generations are metered and charged. When charging is active, cap/insufficient-credit → 402.

Permissions + Drive RBAC

Two-layer model:

  1. Wevion in-app RBAC (getVisibleSessionIds per role)
  2. Google Drive permissions (Service Account owns; user shares explicitly via Drive API)

Troubleshoot

Common: upload fail, thumbnail stuck, AI job pending, AI job failed, Drive sharing broken, credit deduction without result.

FAQ

Drive Service Account vs my Drive?

Wevion uses its own Service Account (workspace-level config). Files belong to the workspace, not individual users.

Can I use Creative Hub files in ads outside Wevion?

Yes — share externally via Drive permissions OR download file.

How long do AI generations take?

Image: 10-60 sec. Video: 1-5 min. Avatar: 2-10 min. TTS: 5-30 sec. Compositing: 30 sec - 5 min.

Provider down — what happens?

Job fails with error_message. No credit charged for failed jobs. Retry / pick different provider.

Can I bulk-export my Creative Hub?

Currently NO bulk export endpoint (DEFERRED feature). Files downloadable individually OR via Drive share to your personal account.

Comments / approval flow on creatives?

Currently NOT implemented (DEFERRED — see PRD-18 deferred articles).

Custom branding for AI-generated content?

Provider-side (some providers accept brand-kit upload). Wevion doesn't centralize brand presets (DEFERRED).

Custom prompt library / reusable prompts?

Currently NOT implemented (DEFERRED).

Next steps

Steps

  1. Wevion in-app RBAC (getVisibleSessionIds per role)
  2. Google Drive permissions (Service Account owns; user shares explicitly via Drive API)

Last updated: 2026-05-17