> 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/views.md).

# Save a records view

A saved view lets you return to the search and columns you use often. Views are separate for People and Companies.

## Save the current view

1. Open **Records → People** or **Companies**.
2. Search for the records you want to return to.
3. Open **Views → Save current view…**.
4. Give the view a recognizable name.
5. Choose its columns and whether to share it with the workspace.
6. Save, then reopen it from **Views** to check the result.

Use a private view for your own working list and a shared view when teammates should use the same setup. Sharing a view does not grant access to the Records feature itself.

## What a view retains

A view keeps its record type, search text, selected columns and sharing choice. It is a saved way to browse current records, rather than an immutable snapshot of the results from the day you saved it.

A view name such as “Enterprise accounts” does not create an industry/headcount rule. Confirm that the saved search actually identifies the intended records. For complex qualification, use explicit [rulebook conditions](/routing/rulebooks.md).

## Use a view for record work

Open the view, select the rows to act on and choose **Run an action**. Actions apply to the selected records and their per-run limits still apply. Saving a view does not schedule enrichment or trigger a CRM write.

See [Browse records](/records/browse.md) and [Batch actions and results](/records/results.md).


---

# 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/views.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.