> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/records/browse.md).

# Browse people and companies

Open **Records**, then choose **People** or **Companies**. People use email as their identity; companies use domain.

Records can come from CSV imports, CRM mirror, website identification and enrichment. They are Distro's stored view of a lead, not a guarantee that the connected CRM has the same values.

## Find a record

Use **Search records** to search email or domain and stored field values. Records appear with recently updated records first. Open a person's email to see their activity.

Use **Views** to return to a saved search and column selection. See [Saved views](/records/views.md).

## Add data

Use **Import CSV** for a file, enable [CRM mirror](/integrations/crm-mirror.md) for CRM fields, or install [Website tracking](/forms/website-tracking.md). A form or enrichment result can also supply data.

If the list is empty, check the workspace, feature access and whether an actual import, sync or identification has happened. Connecting a provider alone does not fill the list.

## Act on selected records

Select the row checkboxes, choose **Run an action**, and choose the action you need. The actions have different effects:

* **Fill gaps** adds missing values.
* **Enrich** replaces values with the provider result.
* **Link to CRM** retains the matching CRM identity.
* **Push to CRM** writes selected fields to that linked record.
* **Web Research** adds research answers.

Read the action guide before running it on a large selection. Provider lookups can consume your provider account's usage; CRM writeback changes the destination record.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/records/browse.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 `build a script that syncs our docs to a CMS` 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.