Asset Folders

Folders give your assets a structure. You can create folders, nest them, and move files between them with drag and drop across projects, organisations, and jobs.

Creating and managing folders

Create folders from any view in the asset browser.
Rename folders by hovering over the folder row and choosing the pencil icon. Type the new name, then press Enter to save or Esc to cancel. Files inside the folder (and any folders nested under it) keep working; their paths update automatically.
Delete folders, with the option to delete the files inside them or keep them. Deleting a folder removes any folders nested under it as well, and if you choose to delete the files, that covers files in the nested folders too. Files you keep return to the root level.

Files that haven’t been placed in a folder appear at the root level, grouped by the team member or agent that created them.

Drag and drop

The asset browser supports two kinds of drag-and-drop:

Move files between folders: drag an existing file onto a folder. The whole folder row (including its file list while expanded) accepts the drop, and the folder opens after the move so you can see where the file landed. Moving a file relocates it rather than copying it, so a file lives in one folder at a time.
Upload from your computer: drag one or more files straight from Finder or Explorer onto a folder to upload them there. A progress bar tracks batch uploads.

You can also:

Move several files at once. Select multiple files first, then drag any of them; the whole selection moves together and the drag preview shows how many files you’re moving.
Move a file out of its folder. While you’re dragging a file that lives in a folder, a Move out of folder target appears above the root file list. Drop the file there to return it to the root level.

Folders you’ve expanded stay expanded while you work, and the folder you’re dragging over is highlighted so you always know where a file will land.

Duplicate handling

Folders keep duplicate handling sensible:

Same name, different folders is fine. /Campaigns/index.md and /Templates/index.md can both exist.
Same name, same folder prompts you. If you upload or move a file whose name already exists in that folder, you’re asked whether to replace it.
Replacing keeps history. Choosing to replace creates a new version of the existing file rather than discarding the old one, so nothing is lost.
Moving several files skips clashes. When you move a multi-file selection and some names already exist in the destination, those files are skipped and a message tells you how many moved, were skipped, or failed. The rest of the selection still moves.

Folders and the Chat Assistant

Ru understands folders too. When you ask Ru to create or save a file in the collection you’re viewing, you can name the folder it should go in (“save it in Campaigns”), and Ru creates the folder if it doesn’t exist yet. Ru can also read and list files inside specific folders, so you can ask about “the brief in the Q3 folder” even when another file has the same name elsewhere in the collection.

Access

Folder operations respect the same access rules as the files themselves: folders belong to a collection, so people only see the folders they’re entitled to. Creating, renaming, moving files between, and deleting folders needs the same permission as uploading assets in that organisation.