> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Collections Overview

> Manage component collections for organizing components

Collections are organizational units that group related components together. They provide logical grouping in the CMS UI without affecting the final package structure (packages flatten all components).

## Collection Object

<ResponseField name="id" type="string">
  Unique identifier (UUID)
</ResponseField>

<ResponseField name="name" type="string">
  Display name
</ResponseField>

<ResponseField name="folderId" type="string">
  Parent folder ID (null for root level)
</ResponseField>

<ResponseField name="createdAt" type="string">
  Creation timestamp (ISO format)
</ResponseField>

<ResponseField name="updatedAt" type="string">
  Last update timestamp (ISO format)
</ResponseField>

<ResponseField name="createdBy" type="string">
  User ID who created the collection
</ResponseField>

<ResponseField name="updatedBy" type="string">
  User ID who last updated the collection
</ResponseField>

### Example Collection

```json theme={null}
{
  "id": "coll123",
  "name": "UI Components",
  "folderId": null,
  "createdAt": "2024-03-20T10:00:00Z",
  "updatedAt": "2024-03-20T10:00:00Z"
}
```

<Note>
  Collections inherit permissions from components. Users need `components.read` to view collections and `components.update` to create, modify, or delete collections.
</Note>