# Library

A **library** groups documents and carries access permissions. Every organization has a
`default` library; creating more is optional.

## Shape

```json
{
  "object": "library",
  "id": "lib_5t7ye1kq0p",
  "name": "Default",
  "is_default": true,
  "visibility": "private",
  "document_count": 42,
  "created_at": "2026-08-10T11:52:16Z"
}
```

## When to use more than one

- Separating customers or projects in a multi-tenant product
- Applying different retention windows per project (Enterprise)
- Restricting which team members can read which uploads

If none of those apply, put everything in `default` and pass `document_ids` explicitly.

## Deleting

Deleting a library deletes its documents and their derived data. It cannot be undone and is rejected
with `409 conflict_error` while an extraction over its documents is still running.

## Not to be confused with

A library is a container, not a query scope. To restrict a Chat to particular sources, pass
`document_ids` — passing a library ID is not supported, because scope must be explicit and auditable.

## Related

documents · document · teams-and-scopes · data-privacy