> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/views.md).
# Views
Use search and **Add filter** to find records in Distro’s collections. Available fields depend on the page: event types can be filtered by availability, language, and duration, while booking links can be filtered by event type and host-related fields.
Select multiple values within a filter when you want to include more than one option. Use its remove control to clear that filter. The sidebar’s **Quick filters** provide common views, such as **In Use** and **Unused** for event types.
## Save a set of filters
After choosing custom filters, click **Save view**. Enter a **View name** and save it. The shortcut appears under **Saved views** in that section’s sidebar.
Saved views are personal to you in the current workspace. They reopen the collection with the saved filters; they do not copy or change the underlying records. The save action is hidden when there are no new custom filters to save, including a filter set you have already saved.
Delete a saved view from its sidebar action when you no longer need the shortcut. Your bookings, links, and other records remain in place.
## Choose how records appear
Use the layout controls where available to switch between table and card views, or between list and calendar views for bookings.
In a table, **Columns** controls which fields appear. Click a column heading to sort, or drag its edge to resize it. These display controls help you review records; they do not change their configuration.
## Review configuration changes
Where available, open **Audit** from a resource’s actions or editor to see recorded configuration changes. You need permission to edit that resource to view its audit. Older configuration can predate audit recording, so an empty history does not mean the resource was never changed.
Use router **Versions** to manage activation and rollback. Audit history records changes; it does not restore them.
Use [Routing Logs](/reporting/routing-logs.md) for an individual prospect's journey and [CRM activity](/crm/activity.md) for personal or group booking-link delivery. These are separate from configuration audits.
---
# 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://help.distro.so/views.md?ask=&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.
