> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/journey-maps/filtering-and-views.md).

# Filters and views

Filter journey maps by persona, tag, or other criteria. Save filter and display settings as named views to return to them later or share with teammates.

See filtering in action, from persona and lane views to combining tags with AND/OR logic and saving the result as a view.

{% embed url="<https://www.youtube.com/watch?v=-6zc9QFVfGw>" %}

#### Why use filters and views

* Focus a busy map on just the persona, tag, or content you care about right now
* Save a filter and display setup as a named view to reopen or share it without rebuilding it each time

#### In this section

* [**Filter a map**](/journey-maps/filtering-and-views/how-to-filter-a-journey-map.md) - Apply filters to focus on specific content.
* [**Save and apply views**](/journey-maps/filtering-and-views/how-to-save-and-apply-a-view.md) - Save a filter and display setup for quick reuse.


---

# 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://helpdesk.smaply.app/journey-maps/filtering-and-views.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.