Advanced Features
Saved Filters & Views
Filters are powerful, but rebuilding the same one every day is tedious. Save the filters you use often, and pin one as your project's default view so it applies automatically to everything you look at.
Two Ways to Reuse a Filter
Flow Myna gives you two complementary tools built on top of filters:
- Saved Filters — give a filter a name and description so you can re-apply it in one click later
- Pinned View — promote one saved filter to be the project's default, so it's always applied on top of every query
Both start the same way: build a filter (manually or via the Co-Pilot), then save it.
Saving a Filter
Once you have one or more filters active:
- Open the filter panel
- Choose Save (the "Pin as View" action in the filter panel footer)
- Give it a clear name—for example, "High-value loans" or "Q1 2024 rejections"
- Optionally add a description explaining what it shows
- Save
The saved filter now lives with your project. Anyone with access to the project can re-apply it.
Name for the Future You
Use names that describe what the filter shows, not when you made it. "High-value, slow loans" is far more useful next month than "Filter 3."
Pinning a View
A pinned view is a saved filter that is always applied. When a view is pinned, its filter is AND-ed into every query in the project:
- The process map
- Variants
- AI-generated insights
- The AI Co-Pilot
- Charts and boards
This is how you set the default lens for everyone—for example, pinning "Completed loans only" so the whole team always analyzes finished cases unless they deliberately look wider.
How to Pin
- Save a filter (above), choosing to pin it—or pin an existing saved filter
- The pinned view appears as a non-removable chip with a lock icon in the Active Filters panel
- Every view in the project now reflects it automatically
At most one view can be pinned per project, so the default is always unambiguous.
Unpinning
To stop a view from applying automatically, unpin it. It remains saved—you can re-apply or re-pin it whenever you like. Unpinning never deletes the filter.
Saved Filter vs. Pinned View
| Saved Filter | Pinned View | |
|---|---|---|
| Applies automatically? | No—re-apply when you want it | Yes—always on, project-wide |
| How many? | As many as you need | At most one per project |
| Shown as | Available to re-apply | Locked chip in the filter panel |
| Use it for | Common scenarios you return to | The project's baseline scope |
Example: Loan Analysis Setup
A team analyzing loan approvals might set up:
- Pinned view: "Completed loans" — so all process maps, variants, and insights exclude in-flight cases by default
- Saved filters they re-apply as needed:
- "High-value (> $75K)"
- "Rejected applications"
- "Took longer than 14 days"
Everyone on the project starts from the same baseline (completed loans), then layers on saved filters to investigate specific questions—without rebuilding anything.
Best Practices
Pin the Baseline, Save the Rest
Use a pinned view for the scope that should always apply (completed cases, a specific region, this fiscal year). Use saved filters for the scenarios you sometimes want.
Keep Pinned Views Conservative
Because a pinned view affects everyone and everything, keep it to broadly-agreed scope. Narrow, exploratory filters are better left as saved (un-pinned) filters.
Describe What Each Filter Shows
A short description turns a personal shortcut into something the whole team can use confidently.
Next Steps
- Filters & Exploration - Build the filters you'll save
- Boards - Pin charts that respect your views and filters
- Collaboration - Share saved analyses with your team
Set It Once, Reuse Forever
Stop rebuilding the same filters. Save the ones you use often, pin the scope that should always apply, and let your project start from the right view every time.