Organize files — folders, rename, move

Last updated: May 19, 2026

Organize files — folders, rename, move

Wevion's folder tree mirrors Google Drive hierarchy. Backed by GET /api/v1/creative-hub/folders/:folderId (verified). Actions: New folder, Rename, Move (drag-drop or menu), Delete. Permissions inherited from parent folder. 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 (folder gets new name on Drive too) + updates creative_hub_file.parent_folder_name cache.

Move

Two ways:

  1. Drag-drop: drag file/folder onto target folder

  2. Action menu → Move → pick destination from modal

Move updates Drive parent + creative_hub_file.drive_folder_id.

Delete

Action menu → Delete → confirm modal.

Delete is soft-delete in Wevion (deleted_at set on creative_hub_file) but hard-delete on Drive (file removed). Recovery: not available within Wevion; would need Drive admin restore from trash within Drive's retention window.

Folder API

GET /api/v1/creative-hub/folders/:folderId (verified apps/backend/src/routes/api/creative-hub-files.route.ts) returns:

  • Folder metadata (name, parent_id, created_at, owner_session_id)

  • Child folders (with count + total size)

  • Child files (with thumbnail URL + size + type)

  • Pagination cursor for infinite scroll

GET /api/v1/creative-hub/root returns your user root folder.

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/   # Feed
google/
  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.

Related