Organize files — folders, rename, move

GET /api/v1/creative-hub/files (+ /breadcrumb). New folder via /folder, rename, move, delete (Drive trash). Drive-backed hierarchy, no DB file table.

Written By Salvatore Sinigaglia

Last updated About 5 hours ago

GET /api/v1/creative-hub/files (+ /breadcrumb). New folder via /folder, rename, move, delete (Drive trash). Drive-backed hierarchy, no DB file table.

Organize files — folders, rename, move

Wevion's folder tree mirrors Google Drive hierarchy. Listing is backed by GET /api/v1/creative-hub/files plus GET /api/v1/creative-hub/breadcrumb (verified); folders are created via POST /api/v1/creative-hub/folder. Actions: New folder, Rename, Move (drag-drop or menu), Delete. There is no creative_hub_file DB table — everything lives on Drive. Naming conventions matter — folders become impossible to navigate without them.

Who is this for

Anyone whose Creative Hub has grown past 50 files. Time to organize.

Folder actions

New folder

Top toolbar → New folder → enter name → confirm.

Folder is created under the current view (root or current subfolder).

Rename

Right-click on folder → Rename OR action menu → Rename. Type new name → enter to confirm.

Rename writes to Drive (the folder gets its new name on Drive). There's no DB cache to update — Drive is the single source of truth.

Move

Two ways:

  1. Drag-drop: drag file/folder onto target folder
  2. Action menu → Move → pick destination from modal

Move re-parents the file/folder on Drive. There is no DB row to update.

Delete

Action menu → Delete → confirm modal.

Delete moves the file/folder to Google Drive trash (trashed: true), falling back to a permanent Drive delete if trashing fails. There is no Wevion soft-delete / deleted_at (no DB file table). Recovery: restore from Drive trash within Drive's retention window.

Folder / listing API

Listing is backed by GET /api/v1/creative-hub/files (files + subfolders for the current folder) and GET /api/v1/creative-hub/breadcrumb (the path). Folders are created via POST /api/v1/creative-hub/folder. There is no /folders/:folderId or /root endpoint — pass the current folder id to /files, and Drive is the source of truth for all metadata.

Folder structure best practices

Per-client (agency setup)

[ClientA]/  campaigns/    spring-sale-2026/      images/      videos/      compositions/  brand-assets/[ClientB]/  ...

Per-campaign (in-house)

campaigns/  spring-sale-2026/    prospecting/    retargeting/  always-on/brand-assets/  logos/  product-shots/ai-generated/  experiments/

Per-platform (if creatives differ heavily)

meta/  9x16/  # Reels/Stories  1x1/   # Feedgoogle/  responsive-display/tiktok/

Pick one model; mixing models destroys findability.

Naming conventions for folders

  • Use kebab-case or snake_case consistently: spring-sale-2026 not Spring Sale 2026
  • Lead with stable prefix: clientA_ makes filtering predictable
  • Date for time-bound campaigns: q1-2026-launch not just launch
  • No special chars: avoid /, \, : (may break Drive sync)

Permissions inheritance

Permissions cascade from parent folder:

  • Wevion RBAC: child folder inherits visibility from parent (set via team folder workflow)
  • Drive permissions: explicit shares (ch-105) apply to specific files / folders; cascade to children by Drive default

To change permissions on a subfolder: explicitly share / unshare at that folder (overrides inheritance).

Bulk operations

For multi-file moves: multi-select (checkbox per file) → action menu → Move to → pick destination. Up to 100 items per batch typical.

Drive vs Wevion view

Files exist in both:

  • Wevion view: Creative Hub UI with thumbnails + actions + Campaign Creator integration
  • Drive view: directly in Google Drive (if shared with user via ch-105)

Both views show the same file (one source of truth on Drive). Renaming in either shows up in the other (with brief sync delay).

Common mistakes

  • Flat structure with 500+ files in one folder: pagination still works but findability is gone. Subdivide.
  • Mixing organizational models: half by client, half by date → confusion. Pick one + commit.
  • Renaming the root folder: don't — breaks the user-folder mapping. Rename subfolders instead.
  • Deleting accidentally: no in-app recovery. Train team on delete-with-care.
  • Spaces in folder names: works but URL-encodes ugly; prefer kebab-case.

FAQ

How do I create and organize folders?

In Wevion's Creative Hub, click New folder in the top toolbar to create one under your current view. Rename via right-click or the action menu, and move files by drag-drop or the Move menu. The folder tree mirrors Google Drive, so a rename or move updates Drive too. Pick one structure model — per-client, per-campaign, or per-platform — and commit to it.

What happens when I delete a folder or file?

Delete moves the file or folder to Google Drive's trash (trashed: true), falling back to a permanent Drive delete if trashing fails. There is no Wevion soft-delete or deleted_at — there's no DB file table at all. To recover, restore it from Drive's trash within Drive's retention window. Train your team to delete with care, and archive old creatives instead.

Do folder permissions apply to subfolders?

Yes — in Wevion's Creative Hub, permissions cascade from the parent folder. Child folders inherit visibility via the team folder workflow, and Drive shares cascade to children by Drive default. To change permissions on a subfolder specifically, explicitly share or unshare at that folder, which overrides the inherited settings.

Can I move multiple files at once?

Yes — Wevion's Creative Hub supports bulk operations. Multi-select files with the checkbox per file, then use the action menu's Move to option and pick a destination. Each move re-parents the item on Google Drive (there's no DB row to update), keeping the Drive tree as the single source of truth.

Can I rename the root folder?

No — don't rename your Creative Hub root folder, because it breaks the user-folder mapping that links your Drive folder to your Wevion account. Rename subfolders instead. When naming folders, use kebab-case or snake_case consistently and avoid special characters like /, \, or :, which can break Drive sync.

Steps

  1. Drag-drop: drag file/folder onto target folder
  2. Action menu → Move → pick destination from modal

Last updated: 2026-05-17