Asset Folders

Folders organise the asset library into a hierarchy. They can be created and managed manually, and the hub can be configured to auto-place new assets into a default folder when they're created from within a playlist.

Folders in the asset library

A folder is a content type (type: 'folder') that lives alongside assets in the asset library and can be nested within other folders.

From the asset library, an admin can:

• Create folders via "Add folder" — multiple folders can be created at once by separating names with commas, semicolons, or new lines
• Navigate folders via breadcrumbs
• Move assets and folders into another folder
• Delete a folder — this cascades, deleting all assets and folders nested within it

See also: Content Structure.

Creating an asset while inside a folder

If an admin is browsing a folder and uses "Create asset" to add a new asset, the asset is created with parent_id set to that folder — it lands inside the folder rather than at the root of the asset library.

Auto-placement of assets created from within a playlist

When a new asset is created directly from within a playlist (rather than via the asset library), the hub can auto-place it into a configured default folder instead of leaving it unfiled at the root of the asset library.

This is configured per-hub under Settings → Default Asset Folders, with two independent settings:

Setting (UI label)	Config key	Applies to
Default folder for content in team playlists	defaultFolderForAssetsCreatedInTeamPlaylist	Assets created with an owning team (ownerTeamId set)
Default folder for content in other playlists	defaultFolderForAssetsCreatedInPlaylist	All other assets created in playlist context

Each setting is a folder path (/-separated nested folder names, created on demand if they don't exist), supporting two template variables resolved at creation time:

• {{team.name}} — the asset's owning team name
• {{playlist.name}} — the playlist the asset is being created in

Rules

• Auto-placement only applies when the asset is created in the context of a playlist (the creation payload includes parentPlaylistId). Assets created directly in the asset library — including inside a folder, see above — are never auto-foldered.
• parent_id and parentPlaylistId are mutually exclusive on asset creation — providing both returns a 400, since an asset can't be both explicitly placed and auto-placed.
• Folders created via auto-placement are recorded in the changelog like any other content-creation event.

These config keys were renamed from createAssetsInFolder / adminCreateAssetsInFolder to make their playlist scope explicit, with a DB migration to carry forward existing hub configuration.