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

# Key concepts

Four ideas carry the rest of the product. Once records, lists, views and deals make sense, agents, reports and the API stop being surprising.

**Records** are the data — every company, contact and deal in your workspace, with standard properties plus any [custom properties](/settings/custom-properties.md) you add. A record exists once, no matter how many lists it appears in.

**Lists** group records of one type. A **Regular list** holds what you (or an agent) put in it. A **Dynamic list** holds whatever currently matches its filters.

**Views** sit on top of a list and change only how you look at it — layout (**Grid** or **Board**), filters, grouping, visible properties, sorting, highlights. That is why one deal list can carry a pipeline board and a focused outreach grid at the same time.

**Deals** are the records that move. Each one belongs to a pipeline and sits in a stage, and advancing that stage is what feeds your boards, forecasts and reports. Track revenue as deal records rather than as a status on the company — the [Deals](/getting-started/key-concepts/records/deals.md) page explains why. Pipelines and stages live in **Settings → Workspace → Pipelines** (see [Pipelines](/settings/pipeline-stages.md)).

Read on: [Records](/getting-started/key-concepts/records.md) for what a record holds and how records relate, [Lists](/getting-started/key-concepts/lists.md) for segmenting, [Views](/getting-started/key-concepts/views.md) for cuts of the same data, [Deals](/getting-started/key-concepts/records/deals.md) for pipelines.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zero.inc/getting-started/key-concepts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.