Filtering in Sheet View should never touch your master sheet. The entire point of a view is to give you a temporary, personal window into your data, one that disappears when you close it, leaving the original untouched. What happened to Chillrends is not a user error; it's a design flaw that breaks trust.
When you create a Sheet View, you expect a safe sandbox. You filter, sort, hide columns, and move on. The master sheet stays pristine, a single source of truth that your colleagues can rely on. But when an advanced filter, especially one applied inside a view, leaks back into the Default view, it doesn't just confuse one person. It corrupts the shared record. Chillrends went back to Default and found the entire sheet transformed into the filter they had set privately. That's the opposite of what a view should do. A view is supposed to protect the master sheet, not overwrite it.
The practical consequence is clear: teams lose confidence in the tool. If you cannot trust that your private filters stay private, you stop using advanced filtering altogether. You go back to clunky workarounds, duplicating tabs, emailing copies, manually re-sorting data. That's not a productivity gain; it's a retreat. Chillrends asked whether it is even possible to use advanced filtering safely with Sheet Views. The honest answer right now is: not reliably, unless you know exactly which filter options trigger the leak. That's not acceptable for a tool meant to accelerate work.
What we need is a hard rule inside the product: any filter applied inside a Sheet View stays inside that view. No exceptions. If a user wants to alter the master sheet, they should have to explicitly apply the filter to Default. Until that boundary is enforced, the feature is half-baked. Chillrends should not have to revert changes by memorizing a recovery workflow. They should be able to filter freely, close the view, and know the master sheet is exactly as they left it. That's the baseline for a tool that claims to empower teams.