> For the complete documentation index, see [llms.txt](https://docs.overflowcms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overflowcms.com/getting-started/core-concepts.md).

# Core Concepts

## Core Concepts

### The hierarchy

```
Workspace  (billing + team; your account's home for everything)
└─ Site      (one dedicated database; usually one per Webflow project)
   └─ Collection   (a content type: Blog, Reviews, Jobs… — you define the fields)
      └─ Item      (one entry in a collection: one blog post, one review…)
```

**Workspace.** The billing and team container. You sign up and get one automatically. Invite teammates or clients into a workspace with a role (owner, admin, editor); they get that role across *every* site in the workspace, not per-site. Plan (and its site/seat caps) lives here — see Plans & Billing.

**Site.** A dedicated database, provisioned when you create it. Deleting a site is dropping its database — clean, and total. Site creation is gated by the workspace's plan (`canAddSite`), and each site gets its own public token for the read API.

**Collection.** A content type with a field schema you define — not a fixed template. A collection's fields can be edited after creation (add/remove/retype fields, rename the collection); existing item data isn't touched unless you actually change a field's key.

**Item.** One entry. Has a `status` (`draft`, `published`, or `scheduled`), a `data` object (the working draft) and, once published, a frozen `publishedData` snapshot that the public API actually serves — so editing a live item never affects what's already public until you hit publish again.

### Fields

Each field has:

* **key** — camelCase, stable identifier used both in the item's JSON `data` and as the `data-oc-field` value in your Webflow markup.
* **type** — one of 9 types (text, richText, image, number, date, boolean, option, reference, video). See Collections & Fields for the full table.
* **required** — enforced on save.
* **indexed** — whether it's usable in filter/sort predicates. Indexed values are extracted into a separate index table at write time specifically so filtering and sorting compile to real SQL instead of scanning JSON blobs.

### Publishing

Publishing an item copies its draft `data` into `publishedData`, flips `status` to `published`, and updates the filter/sort index — all in one step. See Publishing Workflow for drafts, scheduling, and what happens on conflicting edits.

### Public tokens

Each site has one **public token** (`pk_live_…`). It's not a secret — it's meant to sit in your Webflow page's source, the same way an analytics ID does. It grants read-only access to that one site's *published* content only; drafts are never reachable through it. Find it on the site page or any collection's **Integrate** tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overflowcms.com/getting-started/core-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.