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

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

​
Example Content Folder

{
  "id": "folder123",
  "name": "Marketing Content Searches",
  "parentId": null,
  "type": "content",
  "order": 1.0,
  "createdAt": "2024-03-20T10:00:00Z",
  "updatedAt": "2024-03-20T10:00:00Z"
}

​
Example Asset Folder

{
  "id": "folder456",
  "name": "Image Asset Searches",
  "parentId": null,
  "type": "asset",
  "order": 2.0,
  "createdAt": "2024-03-20T10:00:00Z",
  "updatedAt": "2024-03-20T10:00:00Z"
}

​
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:
TypeContains
contentContent saved searches
assetAsset saved searches
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