Skip to main content
Access labels are your organization’s vocabulary for controlling file visibility within workspaces. Build a reusable catalog, then freeze a subset into each workspace at creation time. All list routes use keyset cursor pagination (cursor / next_cursor).

List access labels

Page through the tenant’s label catalog. Query parameters:
  • cursor (optional) — Opaque cursor from a previous page’s next_cursor.
  • limit (optional, default 50, max 200) — Rows per page.
Response:
Response fields:
  • access_label_id — UUID for this catalog entry.
  • name — Slug pattern ([a-z0-9]+(?:_[a-z0-9]+)*, max 64 chars). Immutable after creation.
  • description — Used as the classifier’s prompt when assigning labels during ingestion.

Create access label

Add a label to the tenant catalog. Request:
Body fields:
  • name (required) — Slug pattern, max 64 chars. Must be unique in the tenant catalog.
  • description (required, max 2000 chars) — Write for the classifier — this string IS the classification prompt.
Response (201 Created):
Errors:
  • access_label_name_taken (409) — A label with this name already exists in the tenant catalog.

Get access label

Retrieve one catalog label. Response: Same shape as a Create response.

Update access label

Update a label’s description. Name changes are refused — rename by deleting and creating. Request:
Body fields:
  • description (optional, max 2000 chars) — Updated classifier prompt.
Response (200): Same shape as Create.

Delete access label

Remove a label from the catalog. Response: 204 No Content Errors:
  • access_label_not_found (404) — Label does not exist.
  • access_label_in_use (409) — Label is still referenced by a workspace, a grant, or a file.

Workflow

See Access labels and coverage for the full access-control model.