Skip to main content
Folders provide hierarchical organization for Saved Searches within a project. Each folder has an explicit order field to maintain custom sorting while supporting concurrent edits.
Component Collections serve as the folder mechanism for organizing components, so folders are not used for components.

The Folder Object

string
Unique identifier (UUID)
string
Display name
string
Parent folder ID (null for root level)
string
Folder type: content or asset (must match saved searches it contains)
number
Decimal number for sibling ordering
string
Creation timestamp (ISO format)
string
Last update timestamp (ISO format)

Example Content Folder

Example Asset Folder

Permissions

Folder permissions are inherited from the saved searches they organize:
  • Content folders require content read permissions
  • Asset folders require assets read permissions

Folder Types

Folders are typed to ensure consistency:
Saved searches can only be moved to folders that match their type. Content saved searches cannot be moved to asset folders, and vice versa.

Ordering

The order field uses decimal numbers to allow inserting items between existing items without reordering:
  • Initial items: 1.0, 2.0, 3.0
  • Insert between 1 and 2: 1.5
  • Insert between 1 and 1.5: 1.25